[ovirt-users] Migrating from Fedora 19 to Fedora 20 with oVirt 3.5.0

Sandro Bonazzola sbonazzo at redhat.com
Wed Nov 12 15:09:15 UTC 2014


Il 09/11/2014 00:00, Gianluca Cecchi ha scritto:
> On Thu, Nov 6, 2014 at 7:18 PM, Gianluca Cecchi <gianluca.cecchi at gmail.com>
> wrote:
> 
>>
>>
>>> I've not tested all-in-one upgrade, just to be sure, save current
>>> iptables config and do a backup before starting the upgrade.
>>>
>>>
>>>
>>>>
>>>> Gianluca
>>>>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>>
>>
>>
>> trying to proceed with migration to f20.
>>
>>
> [snip]
> 
> 
>> But I get this with "yum distro-sync"
>>
>> what does it mean?
>>
>> [root at tekkaman sysconfig]# yum distro-sync
>>
>> [snip]
> 
>> --> Running transaction check
>> ---> Package SLOF.noarch 0:0.1.git20121018-1.fc19 will be a downgrade
>> ---> Package SLOF.noarch 0:0.1.git20130430-2.fc19 will be erased
>> ---> Package ipxe-roms-qemu.noarch 0:20130517-2.gitc4bce43.fc19 will be a
>> downgrade
>> ---> Package ipxe-roms-qemu.noarch 0:20130517-3.gitc4bce43.fc19 will be
>> erased
>> ---> Package libcacard.x86_64 2:1.4.2-15.fc19 will be a downgrade
>> ---> Package libcacard.x86_64 2:1.6.1-2.fc19 will be erased
>> ---> Package openbios.noarch 0:1.0.svn1063-2.fc19 will be a downgrade
>> ---> Package openbios.noarch 0:1.1.svn1198-2.fc19 will be erased
>> ---> Package qemu.x86_64 2:1.4.2-15.fc19 will be a downgrade
>> ---> Package qemu.x86_64 2:1.6.1-2.fc19 will be erased
>> ---> Package qemu-common.x86_64 2:1.4.2-15.fc19 will be a downgrade
>> ---> Package qemu-common.x86_64 2:1.6.1-2.fc19 will be erased
>> ---> Package qemu-img.x86_64 2:1.4.2-15.fc19 will be a downgrade
>> ---> Package qemu-img.x86_64 2:1.6.1-2.fc19 will be erased
>> ---> Package qemu-kvm.x86_64 2:1.4.2-15.fc19 will be a downgrade
>> ---> Package qemu-kvm.x86_64 2:1.6.1-2.fc19 will be erased
>>
> 
> 
> In practice the problem is due to the fact that it is an all-in-one
> installation and so it pulled in the virt-preview part for vdsm and related
> packages (qemu-kvm, seabioes, etc..).
> How much is it risky to bypass the "yum distro-sync" step? Will the fedup
> part run itself the distro-sync command then, or is it only a sort of
> pre-check to verify consistency of packages?
> In my case if fedup will retain the ovirt repos all should go ok, correct?

I think it should go ok.

> 
> Gianluca
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



More information about the Users mailing list