Hi,
Am Freitag, 7. Dezember 2012, 09:37:04 schrieb Jan Pazdziora:
> On Fri, Oct 19, 2012 at 01:25:31PM +0200, Michael Calmer wrote:
> > Hi,
> >
> > with the new reboot needed feature introduced some month ago, we realized
> > a
> > small issue.
> >
> > If a patch or package was installed which requires a reboot, the system
> > got
> > the yellow banner on the systems details page.
> >
> > If now a reboot is executed and you look at the page again shortly after
> > the host is up, the banner is still there.
> >
> > The reason is, that the uptime value is updated with first invocation of
> > rhn_check which happen in the default config of rhnsd between 2 and 6
> > hours
> > after rhnsd is started or in case of osad running when the first action is
> > scheduled.
>
> Michael,
>
> I'm sorry I only now got to your post. I have a question here -- I
> assume the banner is there simply because the "system needs reboot"
> condition is based on the rhnServer.last_boot value, being compared to
> the package installation time. And until the server tells Spacewalk
> it has rebooted, Spacewalk assumes it has not.
right
> However, cannot the criteria for system needing reboot be amended
> by also looking at the system's actions, checking if there is
> a reboot.reboot action which was picked up after the package
> installation date / package installation action pickup? That way
> the feature would be purely server-based and work well even with old
> production clients, and the client parts would be an enhancement of
> the logic, not a mandatory part of the setup.
The feature is designed in a way, that also locally triggerd installations are
catched using yum or zypper on the commandline. In such a case, the logged-in
user might also trigger a reboot by himself without using the reboot action
from spacewalk. Looking only for the reboot.rebbot action would then lead into
showing this banner forever.
Additionally these patches solve another issue a lot of our customers have.
They want immediately see in the webui when the last reboot was (after the
system is up again). Waiting ~4 hours until the UI reflect the reality is not
an option for them. Osad does not help in this case, because currently these
data are only submitted, if rhn_check is running. You need to trigger an
action to make osad calling rhn_check.
An enhancement could be, that in case a reboot.reboot action exists, the
message change and say, that a reboot action is already triggered.
--
Regards
Michael Calmer
--------------------------------------------------------------------------
Michael Calmer
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
T: +49 (0) 911 74053 0
F: +49 (0) 911 74053575 - e-mail: michael.cal...@suse.com
--------------------------------------------------------------------------
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
HRB 16746 (AG Nürnberg)
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
