Michael DeHaan wrote: > Michael DeHaan wrote: > >> If you have any /etc/cobbler/*.ks*.rpmnew files, the %post section of >> the RPM will try to delete them, and it will suceed. >> >> The solution looks to be to not have the RPM try to do so much cleanup >> when moving kickstarts to /var/lib/cobbler/kickstarts, and will be >> included in the next release. >> >> Meanwhile, when upgrading cobbler, I'd suggest backing up your >> /etc/cobbler. Cobbler's RPM itself should take care of generating a >> backup of /var/lib/cobbler, though it doesn't hurt to make one of those >> as well, as a generally good practice. Making regular backups of both >> paths is a good idea in general and we should probably create a cobbler >> subcommand to assist with that. >> >> --Michael >> _______________________________________________ >> cobbler mailing list >> [email protected] >> https://fedorahosted.org/mailman/listinfo/cobbler >> >> > > To clarify the rpmnew aspects, it seems this occurs if you have > user-modified any of the sample kickstarts. > > For instance, if you do "cobbler profile report" and you see > "sample.ks", it's a good idea to copy the kickstarts > to something other than sample before the 1.4 upgrade. > > We'll fix this soon. > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
Correction on this -- they do get moved to /var/lib/cobbler/kickstart, but the cobbler objects are not updated. We'll still be tweaking the specfile for the next release, but if this breaks anyone you can just do: "cobbler profile edit --name=foo --kickstart=/var/lib/cobbler/kickstarts/sample.ks" To point cobbler at the new path. For user-generated content the kickstart paths will still be correct. Sorry for the false alarm. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
