Description of problem: Ran yum update on system with RHEV 3.3 Beta and RHEL 6.5 installed. Received an error indicating that rhevm-websocket-proxy was being updated but rhevm explicitly requires the version being removed. This occurs because updating of the rhevm package is "locked" so that only engine-setup can do it. If rhevm-websocket-proxy is to be kept in lockstep with the rhevm package then it should be added to the version lock list, otherwise it breaks regular yum updates for customers. Version-Release number of selected component (if applicable): rhevm-log-collector-3.3.1-2.el6ev.noarch rhevm-websocket-proxy-3.3.0-0.30.beta1.el6ev.noarch rhevm-tools-3.3.0-0.30.beta1.el6ev.noarch rhevm-reports-3.3.0-14.el6ev.noarch rhevm-spice-client-x64-msi-3.3-4.el6_4.noarch rhevm-lib-3.3.0-0.30.beta1.el6ev.noarch rhevm-setup-plugins-3.3.0-1.el6ev.noarch rhevm-userportal-3.3.0-0.30.beta1.el6ev.noarch rhevm-spice-client-x64-cab-3.3-4.el6_4.noarch rhevm-iso-uploader-3.3.0-1.el6ev.noarch rhevm-branding-rhev-3.3.0-1.1.beta1.el6ev.noarch rhevm-webadmin-portal-3.3.0-0.30.beta1.el6ev.noarch quartz-rhevm-1.8.3-5.noarch rhevm-doc-3.3.0-1.el6eng.noarch rhevm-backend-3.3.0-0.30.beta1.el6ev.noarch rhevm-dwh-3.3.0-16.el6ev.noarch rhevm-sdk-python-3.3.0.17-1.el6ev.noarch rhevm-spice-client-x86-msi-3.3-4.el6_4.noarch rhevm-3.3.0-0.30.beta1.el6ev.noarch rhevm-spice-client-x86-cab-3.3-4.el6_4.noarch rhevm-setup-3.3.0-0.30.beta1.el6ev.noarch rhevm-dependencies-3.3.3-1.el6ev.noarch rhevm-restapi-3.3.0-0.30.beta1.el6ev.noarch rhevm-image-uploader-3.3.1-1.el6ev.noarch rhevm-dbscripts-3.3.0-0.30.beta1.el6ev.noarch rhevm-cli-3.3.0.8-1.el6ev.noarch Additional info: --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.32-279.14.1.el6 will be erased ---> Package rhevm-websocket-proxy.noarch 0:3.3.0-0.30.beta1.el6ev will be updated --> Processing Dependency: rhevm-websocket-proxy = 3.3.0-0.30.beta1.el6ev for package: rhevm-3.3.0-0.30.beta1.el6ev.noarch --> Finished Dependency Resolution Error: Package: rhevm-3.3.0-0.30.beta1.el6ev.noarch (@rhel-6-server-rhevm-3-beta-rpms) Requires: rhevm-websocket-proxy = 3.3.0-0.30.beta1.el6ev Removing: rhevm-websocket-proxy-3.3.0-0.30.beta1.el6ev.noarch (@rhel-6-server-rhevm-3-beta-rpms) rhevm-websocket-proxy = 3.3.0-0.30.beta1.el6ev Updated By: rhevm-websocket-proxy-3.3.0-0.34.beta1.el6ev.noarch (rhel-6-server-rhevm-3-beta-rpms) rhevm-websocket-proxy = 3.3.0-0.34.beta1.el6ev Available: rhevm-websocket-proxy-3.3.0-0.25.beta1.el6ev.noarch (rhel-6-server-rhevm-3-beta-rpms) rhevm-websocket-proxy = 3.3.0-0.25.beta1.el6ev You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Avoiding to set this as duplicate of bug #1011087 becuse I rellay hope we can solve this dropping the dependency on a specific 3.3.z-* revision, just requiring >= 3.3.0 in websocket. Alon are you aware of any possible issues in just dropping exact release in wesocket dependencies?
patch merged upstream master, pushed to 3.3 branch.
patch merged on upstream 3.3 branch.
ok, is26. # rpm -q rhevm ; rpm -qR rhevm | grep proxy rhevm-3.3.0-0.38.rc.el6ev.noarch rhevm-websocket-proxy >= 3.3.0-0.38.rc.el6ev
Closing - RHEV 3.3 Released