[Users] Possible problems testing 3.3.3 RC

Hello, engine 3.3.3 beta1 on fedora 19 fully updated (for f19 repos). I would like to upgrade and test 3.3.3 RC I just updated ovirt-release so that now I have ovirt-release-fedora-10.0.1-2.noarch yum clean metadata modified new ovirt repofile enabling updates-testing and disabling beta [ovirt-stable] name=Older Stable builds of the oVirt project baseurl=http://ovirt.org/releases/stable/rpm/Fedora/$releasever/ [ovirt-3.3.2] name=oVirt 3.3.2 release baseurl=http://resources.ovirt.org/releases/3.3.2/rpm/Fedora/$releasever/ [ovirt-updates-testing] name=Test Updates builds of the oVirt project baseurl=http://ovirt.org/releases/updates-testing/rpm/Fedora/$releasever/ Even if ovirt update will be made through engine-setup, I presum that a "yum update" shouldn't give any depedency error, correct? Instead I have: # yum update Loaded plugins: langpacks, refresh-packagekit, versionlock Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-dwh.noarch 0:3.3.3-1.fc19 will be updated ---> Package ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be an update --> Processing Dependency: ovirt-engine-dwh-setup >= 3.4.0-0.2.master.20140122122024.fc19 for package: ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch ---> Package ovirt-engine-lib.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-lib.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-setup.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-setup.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-image-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-image-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-iso-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-iso-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-log-collector.noarch 0:3.3.2-2.fc19 will be updated ---> Package ovirt-log-collector.noarch 0:3.3.3-1.fc19 will be an update --> Running transaction check ---> Package ovirt-engine-dwh-setup.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be installed --> Processing Dependency: ovirt-engine-setup-plugin-ovirt-engine-common for package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch --> Finished Dependency Resolution Error: Package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch (ovirt-updates-testing) Requires: ovirt-engine-setup-plugin-ovirt-engine-common You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Why ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 is proposed as an update? Gianluca

----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "users" <users@ovirt.org> Sent: Thursday, January 23, 2014 12:49:50 PM Subject: [Users] Possible problems testing 3.3.3 RC
Hello, engine 3.3.3 beta1 on fedora 19 fully updated (for f19 repos). I would like to upgrade and test 3.3.3 RC I just updated ovirt-release so that now I have ovirt-release-fedora-10.0.1-2.noarch
yum clean metadata
modified new ovirt repofile enabling updates-testing and disabling beta
[ovirt-stable] name=Older Stable builds of the oVirt project baseurl=http://ovirt.org/releases/stable/rpm/Fedora/$releasever/
[ovirt-3.3.2] name=oVirt 3.3.2 release baseurl=http://resources.ovirt.org/releases/3.3.2/rpm/Fedora/$releasever/
[ovirt-updates-testing] name=Test Updates builds of the oVirt project baseurl=http://ovirt.org/releases/updates-testing/rpm/Fedora/$releasever/
Even if ovirt update will be made through engine-setup, I presum that a "yum update" shouldn't give any depedency error, correct?
Instead I have: # yum update Loaded plugins: langpacks, refresh-packagekit, versionlock Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-dwh.noarch 0:3.3.3-1.fc19 will be updated ---> Package ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be an update --> Processing Dependency: ovirt-engine-dwh-setup >= 3.4.0-0.2.master.20140122122024.fc19 for package: ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch ---> Package ovirt-engine-lib.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-lib.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-setup.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-setup.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-image-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-image-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-iso-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-iso-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-log-collector.noarch 0:3.3.2-2.fc19 will be updated ---> Package ovirt-log-collector.noarch 0:3.3.3-1.fc19 will be an update --> Running transaction check ---> Package ovirt-engine-dwh-setup.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be installed --> Processing Dependency: ovirt-engine-setup-plugin-ovirt-engine-common for package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch --> Finished Dependency Resolution Error: Package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch (ovirt-updates-testing) Requires: ovirt-engine-setup-plugin-ovirt-engine-common You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Why ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 is proposed as an update?
Because it's in the updates repo, not sure why is that. Yaniv/Eyal? -- Didi

On Thu, Jan 23, 2014 at 12:08 PM, Yedidyah Bar David wrote:
Because it's in the updates repo, not sure why is that. Yaniv/Eyal? -- Didi
Indeed I see that 1) In this repo http://resources.ovirt.org/releases/beta/rpm/Fedora/19/noarch/ I would expect dwh for 3.4 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm 2) in this repo http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ I would expect dwh for 3.3.3 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm Gianluca

Il 23/01/2014 12:12, Gianluca Cecchi ha scritto:
On Thu, Jan 23, 2014 at 12:08 PM, Yedidyah Bar David wrote:
Because it's in the updates repo, not sure why is that. Yaniv/Eyal? -- Didi
Indeed I see that
1) In this repo http://resources.ovirt.org/releases/beta/rpm/Fedora/19/noarch/ I would expect dwh for 3.4 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm
2) in this repo http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ I would expect dwh for 3.3.3 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm
It seems that it has been added after 3.3.3-rc announce by mistake. Will fix it
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

On Thu, Jan 23, 2014 at 1:23 PM, Sandro Bonazzola wrote:
Il 23/01/2014 12:12, Gianluca Cecchi ha scritto: [snip]
2) in this repo http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ I would expect dwh for 3.3.3 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm
It seems that it has been added after 3.3.3-rc announce by mistake. Will fix it
OK. It seems now the updates-testing repo is ok: ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm upgrade went smooth. I'm going to test. Gianluca

Il 23/01/2014 14:07, Gianluca Cecchi ha scritto:
On Thu, Jan 23, 2014 at 1:23 PM, Sandro Bonazzola wrote:
Il 23/01/2014 12:12, Gianluca Cecchi ha scritto: [snip]
2) in this repo http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ I would expect dwh for 3.3.3 while I have ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm
It seems that it has been added after 3.3.3-rc announce by mistake. Will fix it
OK. It seems now the updates-testing repo is ok: ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm
upgrade went smooth. I'm going to test.
Yes, updates-testing repo is back to stable: http://jenkins.ovirt.org/job/check_repo_closure/26/
Gianluca
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (3)
-
Gianluca Cecchi
-
Sandro Bonazzola
-
Yedidyah Bar David