This is a multi-part message in MIME format. --------------020300030702030308060904 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sandro Bonazzola wrote: > Il 02/07/2013 15:52, noc ha scritto: > >> Hi All, >> >> I tried yum upgrade on my F18 mgmt-engine server and saw that I don't >> get 3.2.2. Running the following command: >> yum --disablerepo=* --enablerepo=ovirt-stable list >> shows the following (shortened) >> otopi.noarch 1.0.2-1.fc18 >> @ovirt-stable >> otopi-java.noarch 1.0.2-1.fc18 >> @ovirt-stable >> ovirt-engine.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-backend.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-cli.noarch >> 3.2.0.12-1.fc18 @updates >> ovirt-engine-dbscripts.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-dwh.noarch >> 3.2.0-1.fc18 @ovirt-beta >> ovirt-engine-genericapi.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-reports.noarch >> 3.2.0-2.fc18 @ovirt-stable >> ovirt-engine-restapi.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-sdk.noarch >> 3.2.0.11-1.fc18 @updates >> ovirt-engine-setup.noarch >> 3.2.2-1.1.fc18 @ovirt-stable >> ovirt-engine-tools.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-userportal.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-engine-webadmin-portal.noarch >> 3.2.1-1.fc18 @ovirt-stable >> ovirt-host-deploy.noarch >> 1.0.2-1.fc18 @ovirt-stable >> ovirt-host-deploy-java.noarch >> 1.0.2-1.fc18 @ovirt-stable >> ovirt-image-uploader.noarch >> 3.2.2-1.fc18 @ovirt-stable >> ovirt-iso-uploader.noarch >> 3.2.2-1.fc18 @ovirt-stable >> ovirt-log-collector.noarch >> 3.2.2-1.fc18 @ovirt-stable >> ovirt-release-fedora.noarch 7-1 @/ovirt-release-fedora.noarch >> >> Notice the 3.2.1 ovirt-engine.noarch but the 3.2.2-1 ovirt-engine-setup. >> >> Running the same command on a Centos-6.4 engine server gives me the >> expected ovirt-engine-3.2.2-1.1.el6.noarch >> >> Regards, >> >> Joop >> > > It's correct, you now have to run engine-upgrade. It will take care of > updating the rpms to 3.2.2. > 3.2.1 packages will not be listed because of version locking. > > > > Thanks, will try that. It rings a bell that I might have been doing that on my el6 setup. Joop --------------020300030702030308060904 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Thanks, will try that. It rings a bell that I might have been doing that on my el6 setup.Il 02/07/2013 15:52, noc ha scritto:Hi All, I tried yum upgrade on my F18 mgmt-engine server and saw that I don't get 3.2.2. Running the following command: yum --disablerepo=* --enablerepo=ovirt-stable list shows the following (shortened) otopi.noarch 1.0.2-1.fc18 @ovirt-stable otopi-java.noarch 1.0.2-1.fc18 @ovirt-stable ovirt-engine.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-backend.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-cli.noarch 3.2.0.12-1.fc18 @updates ovirt-engine-dbscripts.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-dwh.noarch 3.2.0-1.fc18 @ovirt-beta ovirt-engine-genericapi.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-reports.noarch 3.2.0-2.fc18 @ovirt-stable ovirt-engine-restapi.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-sdk.noarch 3.2.0.11-1.fc18 @updates ovirt-engine-setup.noarch 3.2.2-1.1.fc18 @ovirt-stable ovirt-engine-tools.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-userportal.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-engine-webadmin-portal.noarch 3.2.1-1.fc18 @ovirt-stable ovirt-host-deploy.noarch 1.0.2-1.fc18 @ovirt-stable ovirt-host-deploy-java.noarch 1.0.2-1.fc18 @ovirt-stable ovirt-image-uploader.noarch 3.2.2-1.fc18 @ovirt-stable ovirt-iso-uploader.noarch 3.2.2-1.fc18 @ovirt-stable ovirt-log-collector.noarch 3.2.2-1.fc18 @ovirt-stable ovirt-release-fedora.noarch 7-1 @/ovirt-release-fedora.noarch Notice the 3.2.1 ovirt-engine.noarch but the 3.2.2-1 ovirt-engine-setup. Running the same command on a Centos-6.4 engine server gives me the expected ovirt-engine-3.2.2-1.1.el6.noarch Regards, JoopIt's correct, you now have to run engine-upgrade. It will take care of updating the rpms to 3.2.2. 3.2.1 packages will not be listed because of version locking.