<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Nov 6, 2014 at 7:18 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>
<br>
</div></div>I've not tested all-in-one upgrade, just to be sure, save current iptables config and do a backup before starting the upgrade.<br>
<br>
<br>
<br>
><br>
> Gianluca<br>
<div><div>><br>
<br>
<br>
--<br>
Sandro Bonazzola<br>
Better technology. Faster innovation. Powered by community collaboration.<br>
See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br>
</div></div></blockquote></div><br><br></div></div></div><div class="gmail_extra">trying to proceed with migration to f20.<br><br></div></div></blockquote><div><br>[snip]<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"></div><div class="gmail_extra">But I get this with "yum distro-sync"<br><br></div><div class="gmail_extra">what does it mean?<br></div><div class="gmail_extra"><br>[root@tekkaman sysconfig]# yum distro-sync<br><br></div></div></blockquote><div>[snip] <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">--> Running transaction check<br>---> Package SLOF.noarch 0:0.1.git20121018-1.fc19 will be a downgrade<br>---> Package SLOF.noarch 0:0.1.git20130430-2.fc19 will be erased<br>---> Package ipxe-roms-qemu.noarch 0:20130517-2.gitc4bce43.fc19 will be a downgrade<br>---> Package ipxe-roms-qemu.noarch 0:20130517-3.gitc4bce43.fc19 will be erased<br>---> Package libcacard.x86_64 2:1.4.2-15.fc19 will be a downgrade<br>---> Package libcacard.x86_64 2:1.6.1-2.fc19 will be erased<br>---> Package openbios.noarch 0:1.0.svn1063-2.fc19 will be a downgrade<br>---> Package openbios.noarch 0:1.1.svn1198-2.fc19 will be erased<br>---> Package qemu.x86_64 2:1.4.2-15.fc19 will be a downgrade<br>---> Package qemu.x86_64 2:1.6.1-2.fc19 will be erased<br>---> Package qemu-common.x86_64 2:1.4.2-15.fc19 will be a downgrade<br>---> Package qemu-common.x86_64 2:1.6.1-2.fc19 will be erased<br>---> Package qemu-img.x86_64 2:1.4.2-15.fc19 will be a downgrade<br>---> Package qemu-img.x86_64 2:1.6.1-2.fc19 will be erased<br>---> Package qemu-kvm.x86_64 2:1.4.2-15.fc19 will be a downgrade<br>---> Package qemu-kvm.x86_64 2:1.6.1-2.fc19 will be erased<br></div></div></blockquote></div><br><br></div><div class="gmail_extra">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..).<br></div><div class="gmail_extra">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?<br></div><div class="gmail_extra">In my case if fedup will retain the ovirt repos all should go ok, correct?<br><br></div><div class="gmail_extra">Gianluca<br></div></div>