Bug 1053448

This should not affect 3.3.0 at all. Moving this to QA and proposing to be zstreamed to 3.2.6.

3.2.6 hasn't been released yet.

I manually removed redhat-support-plugin-rhev (--nodeps) and then installed older redhat-support-plugin. After that I ran `engine-setup' and it did not upgraded redhat-support-plugin-rhev to latest version.

It does seem `engine-setup' does not take care if valid rpm versions are installed.

# cat /etc/yum/pluginconf.d/versionlock.list 
rhevm-3.3.0-0.43.el6ev.noarch
rhevm-backend-3.3.0-0.43.el6ev.noarch
rhevm-dbscripts-3.3.0-0.43.el6ev.noarch
rhevm-restapi-3.3.0-0.43.el6ev.noarch
rhevm-tools-3.3.0-0.43.el6ev.noarch
rhevm-userportal-3.3.0-0.43.el6ev.noarch
rhevm-webadmin-portal-3.3.0-0.43.el6ev.noarch
# rpm -qR rhevm | grep redhat-
redhat-support-plugin-rhev >= 3.3.0-13

I also manually removed redhat-support-plugin (--nodeps) and `engine-setup' did not try to install it, it just failed on this:

2014-02-05 14:55:59 DEBUG otopi.context context._executeMethod:137 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/otopi/context.py", line 127, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/system/localstate.py", line 86, in _misc
    os.chown(os.path.join(root, name), uid, gid)
OSError: [Errno 2] No such file or directory: '/var/lib/ovirt-engine/deployments/redhat-support-plugin-rhev.ear'
2014-02-05 14:55:59 ERROR otopi.context context._executeMethod:146 Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/var/lib/ovirt-engine/deployments/redhat-support-plugin-rhev.ear'

What should be valid behavior and valid reproduction steps?

If you use rpm --nodeps for breacking dependencies I'm not really sure engine-setup should be involved.

packages dependencies are determined by yum so if you remove a dependency of an installed package yum can't fix it for you and engine-setup shouldn't do that too.

Once there is a strong dependency between the support plugin and base package, which was forced as to add it to version lock, it can be upgraded only when engine-setup is run. This should be resolved in 3.3 as you can use engine-setup multiple times.

I'm not sure to follow.
On a clean install "yum install rhevm" pull in redhat-support-plugin-rhev

On an upgrade from a clean install engine-setup correctly upgrade redhat-support-plugin-rhev upgrading rhevm group.

"rpm -e --nodeps redhat-support-plugin-rhev" breaks dependencies

"yum install rhevm" now detects rhevm already there and don't pull in again redhat-support-plugin-rhev.

The only thing I think we can do is call "yum check" or  "package-cleanup --problems" and abort if dependency tree is broken. But in any case it should be done in a separate bz.

Jiri,

I don't think it is possible to fix Roman's original problem in 3.2 which is that  'rhevm-upgrade' does not detect when newer versions of the Red Hat support plug-in are available.  

In 3.2 we *tried* to place a dependency between RHEV-M and the plug-in without using version locking.  We did this by adding 'redhat-support-plugin-rhev >= 3.2.1' to the rhevm*.rpm[1].  For a variety of reasons this is not a viable solution.

In 3.3, the plug-in will be in the version lock list.  However, in the meantime 3.2 users will need to do 'rhevm-upgrade' followed by 'yum update redhat-support-plugin-rhev'.

As it relates to this particular BZ, I suggest that we close it with 'NEXTRELASE'

Sandro/Alon: Do you agree?

Keith

[1] https://rhn.redhat.com/network/software/packages/dependencies.pxt?pid=832869

Keith, I'm not sure to follow.

Upgrading to >= 3.3.0 will upgrade both rhevm and redhat-support-plugin-rhev to latest 3.3.z version available.
In >= 3.3.0 redhat-support-plugin-rhev is not under version locking anymore: we had an agreement that 3.4 will be backward compatible to 3.3 allowing the upgrade using yum update.

In 3.2.5 redhat-support-plugin-rhev is under version locking.
So if you release any new version in 3.2.z you'll have to run rhevm-upgrade in order to upgrade it. If rhevm-upgrade already update redhat-support-plugin-rhev this bug can be closed as not a bug. 
Otherwise this bug is not relevant on 3.3 (no locking) but only on 3.2, where rhevm-upgrade must be fixed for allowing the upgrade of a new version of redhat-support-plugin-rhev in 3.2.z.

This is for 3.3, so please provide valid verification steps otherwise I can't verify. Thanks.

separate BZ1063941 opened to correct code to find YUM group, otherwise this BZ is verified.

[root@pb-rh33 setup]# egrep 'RHEV Manager|redhat-support-plugin' /var/log/ovirt-engine/setup/ovirt-engine-setup-20140211172614.log
2014-02-11 17:26:27 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages.verbose:177 Yum: queue group RHEV Manager for update
2014-02-11 17:26:29 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages.verbose:177 Yum: group RHEV Manager queued
2014-02-11 17:26:29 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages.verbose:177 Yum:     updated    - redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:29 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages.verbose:177 Yum:     update     - redhat-support-plugin-rhev-3.3.0-14.el6ev.noarch
2014-02-11 17:26:29 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:240 PACKAGE: [updated] redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:29 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:240 PACKAGE: [update] redhat-support-plugin-rhev-3.3.0-14.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [available] package redhat-support-plugin-rhev-3.3.0-14.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [installed] package redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [reinstall_available] package redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [available] package redhat-support-plugin-rhev-3.3.0-14.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [installed] package redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:30 DEBUG otopi.plugins.ovirt_engine_setup.distro-rpm.packages packages._checkForProductUpdate:254 dupes: operation [reinstall_available] package redhat-support-plugin-rhev-3.3.0-13.el6ev.noarch
2014-02-11 17:26:37 DEBUG otopi.context context.dumpEnvironment:456 ENV OSETUP_RPMDISTRO/versionLockFilter=list:'['rhevm', 'redhat-support-plugin-rhev']'

ok, verified as BZ1067682 is solving root cause on 3.3.x - yum group.