Stephen John Smoogen wrote: > Well I was doing some house cleaning today.. in trying to add red hat > distro 5.3 to the cobbler box etc. I did what I normally do > > > > cobbler import --breed=redhat --arch=i386 --mirror=/mnt/iso/ > --name=rhel-5.3-server-i386 > > geta list of 5.2 systems and move them to 5.3 > > for i in cain1_unm_edu cain2_unm_edu cellini_unm_edu crux_unm_edu > docbook-new_unm_edu enyo_unm_edu eprint_new_unm_edu megrez_unm_edu > pallas_unm_edu quasi_unm_edu scheat_unm_edu sedna_unm_edu > thrymr_unm_edu varuna_unm_edu vm-banana-t_unm_edu vortigern_unm_edu > zimbra2_unm_edu; do cobbler system edit --name=$i > --profile=rhel-5.3-server-i386; done >
This looks fine. > cobbler list shows them pointing to the right profile. > > I am running out of space and need to update others so I did a > > cobbler profile remove --name=rhel-5.2-server-i386 > cobbler distro remove --name=rhel-5.2-server-i386 > Without specifying --recursive, even the above removal would not delete any child systems. > and Pow.. no more systems when I do a cobbler systems list.. Not sure > where they went or why they went away.. the directory > /var/lib/cobbler/config/systems.d/ is empty. > The above commands should not cause that result; short of "cobbler reserialize" there is nothing in cobbler anymore that saves each and every cobbler object when something changes (assuming you are using serializer_catalog in modules.conf, which nearly everything but the oldest of installations would be using -- this is the one that uses systems.d, as opposed to the ancient /var/lib/cobbler/systems file). > What did I do wrong? > > Don't know. I really don't want there to be a bug this fundamental anywhere; and I also think someone would have hit it already if there was such a problem. I'd be interested if you can replicate this. Did you install cobbler systems after midnight or get them too close to water? (A good lesson regardless -- backup your /var/lib/cobbler dirs, as well as /etc/cobbler.) Let me know if you can figure out anything else. Might be a good idea to check /var/log/cobbler/*.log for any obvious exceptions just in case there is anything there that could help shed some light on things. (Also, bash history, just in case there is something else missing?) --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
