UsrMove feature breaking "yum upgrade" upgrades from older releases to F17?

[Reindl Harald]

Am 26.01.2012 14:08, schrieb Nils Philippsen:
> For the sake of completeness:
> 
> On Thu, 2012-01-26 at 03:22 +0100, Reindl Harald wrote:
>> after a yum upgrade you can verify that the most important
>> things are fine BEFORE reboot (bootloader-config,
>> package-cleanup --problems, ....), optimize/correct things
>> you know are not fine after the upgrade (active services
>> after transition to systemd as example) and then you reboot
>> ONCE in a clean starting system instead a boot in the blue
> 
> ... as can be done on VC2 after updating with anaconda

while the system and services are running?
show me how you will do this!

you are missing the point that "yum distro-sync" is running
while the system is up and can be distributed after testing
AUTOMATICALLY to 10,20,30,100 machines followed by a 30
seconds reboot

shutdown the VM, insert the ISO and boot anaconda takes much
longer as the whole upgrade via yum - our machines needed
between 4 and 6 minutes each server for the whole F14->F15
upgrade, so in an hour you have all machines updated with
nearly zero downtime

a change which damages this capabilities has to be fixed

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120126/ff4f0629/attachment-0001.sig>