On 12/23/13 01:56, Sandro Bonazzola wrote:
I think the problem may be other than I indicated, however, because I don't see ovirt-engine-3.3.2 in the FC19 stable repo either. Here's the error output of my update command:
Error: Package: ovirt-engine-3.3.1-2.el6.noarch (@ovirt-stable) Requires: ovirt-engine-websocket-proxy = 3.3.1-2.el6 Removing: ovirt-engine-websocket-proxy-3.3.1-2.el6.noarch (@ovirt-stable) ovirt-engine-websocket-proxy = 3.3.1-2.el6 Updated By: ovirt-engine-websocket-proxy-3.3.2-1.el6.noarch (ovirt-3.3.2) ovirt-engine-websocket-proxy = 3.3.2-1.el6 Available: ovirt-engine-websocket-proxy-3.3.0-3.el6.noarch (ovirt-stable) ovirt-engine-websocket-proxy = 3.3.0-3.el6 Available: ovirt-engine-websocket-proxy-3.3.0-4.el6.noarch (ovirt-stable) ovirt-engine-websocket-proxy = 3.3.0-4.el6 Available: ovirt-engine-websocket-proxy-3.3.0.1-1.el6.noarch (ovirt-stable) ovirt-engine-websocket-proxy = 3.3.0.1-1.el6 Available: ovirt-engine-websocket-proxy-3.3.1-1.el6.noarch (ovirt-stable) ovirt-engine-websocket-proxy = 3.3.1-1.el6 This is a bug in ovirt-engine-3.3.1 dependencies fixed in 3.3.2 (Bug 1033629 - Unable to run regular yum update due to implicit (undeclared) version lock on rhevm-websocket-proxy )
Il 20/12/2013 17:23, Bob Doolittle ha scritto: please follow upgrade path as in release notes:
# yum update ovirt-release # yum repolist enabled # yum update ovirt-engine-setup # engine-setup
This did the trick. Thanks Sandro. -Bob