[Spacewalk-list] Schedling & Action Chain Timing Question

[Matt Bayliss]

OK, so I've doing some more testing on this - since I couldn't remember
preciseley the time I submitted the previous jobs so I've recorded times
more accurately now.

Yesterday morning between 1045-1100 GMT I submitted a number of jobs to run
at 9AM over the next 4 days too see when they were picked up and executed.
The first job was scheduled to execute today after 9AM, according to the
schedule its showing:


   -  *Summary:*
    Package Install scheduled by mattb
    -  *Details:*
    This action will be executed after 12/23/14 9:00:00 AM GMT
   This action's status is: Queued.
   This action has not yet been picked up.
   Packages Scheduled:
   - kernel-2.6.32-504.3.3.el6.x86_64
      - rsyslog-5.8.10-10.el6_6.x86_64
      - kernel-firmware-2.6.32-504.3.3.el6.noarch
    -  *Time:*
    12/23/14 9:00:00 AM GMT

I'm surprised that the action "has not yet been picked up" since the server
checked in (via the spacewalk proxy) just 35 minutes before the "execute
after" time.

I've checked and times on the three involved nodes (spacewalk, proxy &
client) are all in sync.

Regards,




On 19 December 2014 at 12:10, Matt Bayliss <aarrgghh765 at gmail.com> wrote:

> I scheduled a jobs on the morning of the 17th December to execute the
> following morning at 9AM, it seems that although the rhnsd interval is set
> to 240 [1] the job was not picked up and executed until approx 28 hours
> after I created the schedule.
>
> [1] # cat /etc/sysconfig/rhn/rhnsd
> INTERVAL=240
>
>
>     Summary:
>     Package Install scheduled by swadmin
>     Details:
>     This action will be executed after 12/18/14 9:00:00 AM GMT
>     This action's status is: Completed.
>     The client picked up this action on 12/18/14 3:03 PM
>     The client completed this action on 12/18/14 3:05 PM
>     Client execution returned "Update Succeeded" (code 0)
>     Packages Scheduled:
>         nss-util-3.16.2.3-2.el6_6.x86_64
>         rpm-python-4.8.0-38.el6_6.x86_64
>         rpm-4.8.0-38.el6_6.x86_64
>         system-config-firewall-base-1.2.27-7.2.el6_6.noarch
>         selinux-policy-3.7.19-260.el6_6.1.noarch
>         nss-3.16.2.3-3.el6_6.x86_64
>         nss-sysinit-3.16.2.3-3.el6_6.x86_64
>         rpm-build-4.8.0-38.el6_6.x86_64
>         nss-tools-3.16.2.3-3.el6_6.x86_64
>         ruby-1.8.7.374-3.el6_6.x86_64
>         ruby-libs-1.8.7.374-3.el6_6.x86_64
>         rpm-libs-4.8.0-38.el6_6.x86_64
>         selinux-policy-targeted-3.7.19-260.el6_6.1.noarch
>     Time:
>     12/18/14 9:00:00 AM GMT
>
> Also, this job was pard of an action chain to reboot the system when the
> package update was complete (not necessary but I wanted to test it) this
> was not completed until 4-5 hours after the package update which would have
> only taken a few minutes.  I'm surprised that this didn't happen
> immediately afterward.
>
> Summary:
> System reboot scheduled by mattb
> Details:
> This action will be executed after 12/18/14 9:00:00 AM GMT
> This action's status is: Completed.
> The client picked up this action on 12/18/14 3:05 PM
> The client completed this action on 12/18/14 7:48 PM
> Client execution returned "null" (code null)
> Time:
> 12/18/14 9:00:00 AM GMT
>
> Am I misunderstanding how the scheduler works?  I won't be able to rely on
> this in production if I can't predict with some accuracy when the jobs will
> execute.
>
> Regards,
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141223/c20072e2/attachment.htm>