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

Gianluca Cecchi gianluca.cecchi at gmail.com
Thu Nov 6 18:18:32 UTC 2014 

On Fri, Oct 24, 2014 at 8:05 AM, Sandro Bonazzola <sbonazzo at redhat.com>
wrote:

> Il 23/10/2014 17:58, Gianluca Cecchi ha scritto:
> > On Thu, Oct 23, 2014 at 5:52 PM, Sandro Bonazzola <sbonazzo at redhat.com>
> > wrote:
> >
> >> Hi,
> >> just finished testing migration path from F19 to F20 for systems running
> >> oVirt.
> >> F19 is going EOL one month after F21 release which is currently planned
> >> for December 2nd.
> >>
> >> If you're running oVirt on Fedora 19 I suggest you to do it once
> finished
> >> to upgrade oVirt to 3.5.0.
> >> I've saved some notes in the test request bug[1]:
> >> Bug 1131828 - Test upgrade path from Fedora 19 with oVirt 3.5.z to
> Fedora
> >> 20
> >>
> >> Enjoy!
> >>
> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1131828
> >>
> >>
> > NIce to hear this.
> > I'm going to do it and give feedback on one of my personal workstations
> > that is currently on F19 with all-in-one 3.4.4 due to this.
> > Do you think the workflow is ok also for an all-in-one environment?
>
> 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.

yum update gives nothing:
[root at tekkaman sysconfig]# yum update
Loaded plugins: fastestmirror, langpacks, refresh-packagekit, versionlock
Loading mirror speeds from cached hostfile
 * fedora: ftp-stud.hs-esslingen.de
 * livna: rpm.livna.org
 * ovirt-3.4-stable: ftp.snt.utwente.nl
 * ovirt-3.5: ftp.snt.utwente.nl
 * rpmfusion-free: mirror.de.leaseweb.net
 * rpmfusion-free-updates: mirror.de.leaseweb.net
 * rpmfusion-nonfree: mirror.de.leaseweb.net
 * rpmfusion-nonfree-updates: mirror.de.leaseweb.net
 * updates: ftp-stud.hs-esslingen.de
No packages marked for update

But I get this with "yum distro-sync"

what does it mean?

[root at tekkaman sysconfig]# yum distro-sync
Loaded plugins: fastestmirror, langpacks, refresh-packagekit, versionlock
Dropbox
|  951 B  00:00:00
adobe-linux-x86_64
|  951 B  00:00:00
google-chrome
|  951 B  00:00:00
livna
| 1.3 kB  00:00:00
ovirt-3.4-fedora-virt-preview
| 2.9 kB  00:00:00
ovirt-3.4-stable
| 2.9 kB  00:00:00
ovirt-3.5
| 2.9 kB  00:00:00
ovirt-3.5-fedora-virt-preview
| 2.9 kB  00:00:00
ovirt-3.5-patternfly1
| 3.0 kB  00:00:00
rpmfusion-free-updates
| 3.3 kB  00:00:00
rpmfusion-nonfree-updates
| 3.3 kB  00:00:00
updates/19/x86_64/metalink
|  28 kB  00:00:00
Loading mirror speeds from cached hostfile
 * fedora: ftp-stud.hs-esslingen.de
 * livna: rpm.livna.org
 * ovirt-3.4-stable: ftp.snt.utwente.nl
 * ovirt-3.5: ftp.snt.utwente.nl
 * rpmfusion-free: mirror.de.leaseweb.net
 * rpmfusion-free-updates: mirror.de.leaseweb.net
 * rpmfusion-nonfree: mirror.de.leaseweb.net
 * rpmfusion-nonfree-updates: mirror.de.leaseweb.net
 * updates: ftp-stud.hs-esslingen.de
Resolving Dependencies
--> 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
---> Package qemu-system-alpha.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-alpha.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-arm.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-arm.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-cris.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-cris.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-lm32.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-lm32.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-m68k.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-m68k.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-microblaze.x86_64 2:1.4.2-15.fc19 will be a
downgrade
---> Package qemu-system-microblaze.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-mips.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-mips.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-or32.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-or32.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-ppc.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-ppc.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-s390x.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-s390x.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-sh4.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-sh4.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-sparc.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-sparc.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-unicore32.x86_64 2:1.4.2-15.fc19 will be a
downgrade
---> Package qemu-system-unicore32.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-x86.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-x86.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-system-xtensa.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-system-xtensa.x86_64 2:1.6.1-2.fc19 will be erased
---> Package qemu-user.x86_64 2:1.4.2-15.fc19 will be a downgrade
---> Package qemu-user.x86_64 2:1.6.1-2.fc19 will be erased
---> Package seabios-bin.noarch 0:1.7.2.2-3.fc19 will be a downgrade
---> Package seabios-bin.noarch 0:1.7.3.1-1.fc19 will be erased
---> Package seavgabios-bin.noarch 0:1.7.2.2-3.fc19 will be a downgrade
---> Package seavgabios-bin.noarch 0:1.7.3.1-1.fc19 will be erased
---> Package sgabios-bin.noarch 1:0.20110622svn-5.fc19 will be a downgrade
---> Package sgabios-bin.noarch 1:0.20110622svn-6.fc19 will be erased
---> Package virt-install.noarch 0:0.10.0-5.fc19 will be a downgrade
---> Package virt-install.noarch 0:0.10.0-5.git1ffcc0cc.fc19 will be erased
---> Package virt-manager-common.noarch 0:0.10.0-5.fc19 will be a downgrade
---> Package virt-manager-common.noarch 0:0.10.0-5.git1ffcc0cc.fc19 will be
erased
--> Finished Dependency Resolution
Error: Package: 2:qemu-system-moxie-1.6.1-2.fc19.x86_64
(@fedora-virt-preview)
           Requires: qemu-common = 2:1.6.1-2.fc19
           Removing: 2:qemu-common-1.6.1-2.fc19.x86_64
(@fedora-virt-preview)
               qemu-common = 2:1.6.1-2.fc19
           Downgraded By: 2:qemu-common-1.4.2-15.fc19.x86_64 (updates)
               qemu-common = 2:1.4.2-15.fc19
           Available: 2:qemu-common-1.4.2-3.fc19.x86_64 (fedora)
               qemu-common = 2:1.4.2-3.fc19
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

my repos config;

[root at tekkaman sysconfig]# ls -1  /etc/yum.repos.d/*repo
/etc/yum.repos.d/adobe-linux-x86_64.repo
/etc/yum.repos.d/dropbox.repo
/etc/yum.repos.d/fedora.repo
/etc/yum.repos.d/fedora-updates.repo
/etc/yum.repos.d/fedora-updates-testing.repo
/etc/yum.repos.d/google-chrome.repo
/etc/yum.repos.d/livna.repo
/etc/yum.repos.d/ovirt-3.4-dependencies.repo
/etc/yum.repos.d/ovirt-3.4.repo
/etc/yum.repos.d/ovirt-3.5-dependencies.repo
/etc/yum.repos.d/ovirt-3.5.repo
/etc/yum.repos.d/rpmfusion-free-rawhide.repo
/etc/yum.repos.d/rpmfusion-free.repo
/etc/yum.repos.d/rpmfusion-free-updates.repo
/etc/yum.repos.d/rpmfusion-free-updates-testing.repo
/etc/yum.repos.d/rpmfusion-nonfree-rawhide.repo
/etc/yum.repos.d/rpmfusion-nonfree.repo
/etc/yum.repos.d/rpmfusion-nonfree-updates.repo
/etc/yum.repos.d/rpmfusion-nonfree-updates-testing.repo

In the past when this system was with oVirt 3.x and x <3  I think I had
virt-preview enabled, but now I have only
/etc/yum.repos.d/fedora-virt-preview.repo.rpmsave
because virt-preview is in
/etc/yum.repos.d/ovirt-3.4-dependencies.repo
/etc/yum.repos.d/ovirt-3.5-dependencies.repo


 [root at tekkaman sysconfig]# diff
/etc/yum.repos.d/ovirt-3.4-dependencies.repo
/etc/yum.repos.d/ovirt-3.5-dependencies.repo1c1
< [ovirt-3.4-fedora-virt-preview]
---
> [ovirt-3.5-fedora-virt-preview]
7a8,15
>
> [ovirt-3.5-patternfly1]
> name=Copr repo for patternfly1 owned by patternfly
> baseurl=
http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/fedora-$releasever-$basearch/
> enabled=1
> skip_if_unavailable=1
> gpgcheck=0
>

Thanks for help,
Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20141106/305e2088/attachment-0001.html>

More information about the Devel mailing list