On 8/17/10 3:34 PM, James Hogarth wrote:
On 17 August 2010 20:26, James Hogarth<[email protected]>  wrote:
Hi all,

Just a note in case this causes headaches for anyone else....

I accidentally updated cobbler to 2.0.3 when I did a yum upgrade ....
broke spacewalk in a pretty bad way for the kickstart/cobbler side and
nearly had to revert my VM to spacewalk 1.0 and start again...
couldn't even install cobbler from the spacewalk channel...
fortunately was able to rpm -e --nodeps cobbler and install from the
old rpm in the /var/satellite/redhat rpm archives...

Make sure you stay on cobbler 1.6.6!

If you are missing the rpm (EPEL no longer has it) I can email it to you.

James

ignore the channel issues - that was a messed up
/etc/sysconfig/up2date .... but my kickstarts and admin/cobbler/sync
still resulted in tracebacks and cobblerd couldn't start after an
update from 1.6.6 to 2.0.3 ...
Any idea why cobbler couldn't start? I'm running an up to date version of cobbler here.

-Justin

James

_______________________________________________
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

Reply via email to