[et-mgmt-tools] cobbler/koan/python-cheetah blocking yum upgrade?

[Michael DeHaan]

Bill McGonigle wrote:
> On Nov 14, 2007, at 15:39, Michael DeHaan wrote:
>
>> Those packages are not in the f7 "core" repo you have, hence the 
>> problem.
>
> python-cheetah is in there, at least. cobbler and koan are in the 
> updates repo - I *think* yum does the right thing there, but maybe not.
>
> It could also be that I'm not using cobbler reposync properly - 
> previously I was rsyncing mirrors with my own scripts, which I'm 
> looking forward to abandoning in favor of cobbler's! Do these look 
> appropriate?:
>

You really need to upgrade using the CD so Anaconda can come into the 
picture, and then upgrade cobbler after you finish the CD install. I 
don't believe yum upgrades from FC6 -> F7 were supposed to work.

(Fortunately, there are such a thing as upgrade kickstarts, if you need 
to do a rollout to upgrade a lot of systems... so, yes, you could 
technically use Cobbler to upgrade other systems via PXE and/or koan
after you get that done)


> ---
> -
> arch: ''
> createrepo_flags: -c cache
> depth: 2
> keep_updated: True
> mirror: 
> 'http://mirror.anl.gov/pub/fedora/linux/releases/7/Everything/i386/os'
> name: f7i386
> parent: ~
> rpm_list: ''
> -
> arch: ''
> createrepo_flags: -c cache
> depth: 2
> keep_updated: True
> mirror: 'http://mirrors.kernel.org/fedora/updates/7/i386/'
> name: f7i386updates
> parent: ~
> rpm_list: ''
>
> Aside: the docs use repo names like this, but yum doesn't seem to be 
> able to interpret "$basearchupdates", so f7i386-updates might be a 
> better doc example, since yum can handle "$basearch-updates".
>
>> AFAIK Anaconda upgrades will update everything they can and leave the 
>> other packages out, which you could then update later.
>
> Come to think of it, yum skip-broken might handle this as well. Just 
> for grins, if I were to:
>
> rpm -e python-cheetah cobbler koan
>
> would I lose my data and config files or just the programs and rpmdb 
> entries? I could re-install the packages right after upgrade.
>
>> AFAIK upgrading directly from yum (versus a CD) is usually not 
>> recommended.
>
> Yeah, that's the official position, but virtualization makes this even 
> tougher - I'd have to take down 8 'machines' for a long time vs just a 
> quick reboot. Before xen, only one machine was affected; online 
> upgrades are an even bigger win today.
>
> Despite the official position, I have machines that work great having 
> been yum upgraded from RH9 to F7, so far, F8 I'm just starting with.
>
> This is all predicated on my observation that F7 and F8 don't work 
> under an FC6 cobbler/xen install. If others have contrary experience, 
> I'd sure like to hear it - that would take some pressure off an 
> upgrade timeframe. I've looked for a matrix/docs of which versions of 
> Fedora and/or Xen Dom0's can host which versions in DomU's, but I 
> haven't been able to find it yet. On the latest cobbler/koan under FC6 
> I can deploy other FC6 no problem, but F7 and F8 cause the Xen guest 
> to crash during boot (according to xend.log).
>
> Thanks,
> -Bill
>
> -----
> Bill McGonigle, Owner Work: 603.448.4440
> BFC Computing, LLC Home: 603.448.1668
> bill at bfccomputing.com Cell: 603.252.2606
> http://www.bfccomputing.com/ Page: 603.442.1833
> Blog: http://blog.bfccomputing.com/
> VCard: http://bfccomputing.com/vcard/bill.vcf
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools