[Spacewalk-list] Needs-Restarting shows perpetual reboot need after Kickstart

[bryan.norton at gmail.com]

It looks like it was a date/time issue.  When the system was kickstarted, it
used the default GMT.  Somewhere in the update process after install, the
time was corrected to GMT+2.  After 2 hours, I rebooted it again, and no it
no longer thinks it needs to reboot to load a more recent kernel, and shows
the system is up to date.

 

From: bryan.norton at gmail.com <bryan.norton at gmail.com> 
Sent: Friday, July 19, 2019 06:11
To: spacewalk-list at redhat.com
Subject: Needs-Restarting shows perpetual reboot need after Kickstart

 

Since I couldn't get around the Internal Server Error when attempting to
Profile Sync, I found a work around using spacecmd and a post script during
the Kickstart process.

 

Everything works great, with one exception.  After the provisioning is done,
and the server is accessible, it shows that it needs a reboot.  After
rebooting it, it still shows a reboot is needed.  It says (amongst other
components) that the kernel has been updated, yet uname -r shows it is
running the kernel that it thinks it needs to reboot to use.

 

Have you all seen this before?  I'm stumped.no amount of googling has
produced anything close to helpful.

 

Thanks!

Bryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190719/b913b54a/attachment.htm>