Was the new provision, registered? You also check if reboot actioned is not being overriden on client.
[root@client3 ~]# rhn-actions-control --report deploy is enabled diff is enabled upload is enabled mtime_upload is enabled run is enabled [root@client3 ~]# grep boot /etc/sysconfig/rhn/up2date disallowConfChanges=noReboot;sslCACert;useNoSSLForPackages;noSSLServerURL;serverURL;disallowConfChanges noReboot[comment]=Disable the reboot actions noReboot=0 and you can trigger it manually after it's scheduled on spacewalk server on client run rhn_check. rhn_check -vvvv Cheers, Lupin On Tue, Oct 29, 2013 at 1:09 AM, raj kumar <[email protected]> wrote: > I got a strange problem. Even though I selected to "reboot" in profile, > after kickstart, the system is not rebooting after successful installation. > > I've create a new profile for centos64 with some of the post scripts for > customization. after all the scripts executed the system does nothing. I > have to reboot manually. > > Kickstarting vmware esxi guests using spacewalk1.9. > > any inputs, please? > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
