Hi,

In https://gerrit.ovirt.org/#/c/62672 we removed the release from vdsm* requirements. Although it sounds reasonable and quite safe, it was not.

In development env it causes mixup of versions when upgrading.

"yum install vdsm" will eventually cause this mixup as vdsm won't require the newer vdsm-python

I think this change should be reverted and the solution should be in the build process. Newer release is equal to higher version, requirement should include the release number.

so for example, 4.18.7-1 was shipped and for ppc we built 4.18.7-2 so 4.18.7-2 is newer. can't see how this can be different.

e.g for the bug:

===================================================================================================================================================================================================================

Package Arch Version Repository Size

Removing:

vdsm x86_64 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 2.7 M

vdsm-api noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 325 k

vdsm-cli noarch 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 342 k

vdsm-hook-vmfex-dev noarch 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 21 k

vdsm-jsonrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 81 k

vdsm-python noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 2.4 M

vdsm-xmlrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 109 k

vdsm-yajsonrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 95 k

Problem.

Yaniv Bronhaim.