RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 870079 - 3.1 - packaging: vdsm and vdsm-cli conflict causes rhevm-3.0 bootstrap to fail
Summary: 3.1 - packaging: vdsm and vdsm-cli conflict causes rhevm-3.0 bootstrap to fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Alon Bar-Lev
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
: 870315 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-25 14:20 UTC by Dafna Ron
Modified: 2022-07-09 05:39 UTC (History)
11 users (show)

Fixed In Version: vdsm-4.9.6-40.0
Doc Type: Bug Fix
Doc Text:
The VDSM and vdsm-cli packages were changed in 3.1 in a way that creates a conflict with previous packages if VDSM and vdsm-cli are not upgraded at the same yum transaction. rhevm-3.0 tries to upgrade VDSM and vdsm-cli in different yum transactions and fails because of that conflict. Now, vdsm-cli is a dependency of vdsm and is pulled into the vdsm yum transaction, allowing yum to resolve the conflict.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:13:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 855887 0 high CLOSED vdsm: reinstall of host when vdsm repo was updated from 4.9-113.3 to vdsm-4.9.6-32.0 fails on Transaction Check Error 2022-07-09 05:39:30 UTC
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC
oVirt gerrit 35722 0 'None' 'MERGED' 'Using with_rhev flag in spec to configure rhev changes if required' 2019-11-27 14:03:11 UTC

Internal Links: 855887

Description Dafna Ron 2012-10-25 14:20:17 UTC
Description of problem:

in the past we did not need to run yum update 'vdsm*' ore remove vdsm-cli before running update for vdsm to succeed update. 

now, when I update 3.0 vdsm to 3.1 vdsm we get a conflict: 

file /usr/share/vdsm/dumpStorageTable.py from install of vdsm-4.9.6-39.0.el6_3.x86_64 conflicts with file from package vdsm-cli-4.9-113.4.el6_3.x86_64

Version-Release number of selected component (if applicable):

4.9-113.4.el6_3.x86_64 -> vdsm-4.9.6-39.0.el6_3.x86_64

How reproducible:

100%

Steps to Reproduce:
1. have a host with 3.0 vdsm
2. run yum update vdsm 
3.
  
Actual results:

we fail on clonflict with vdsm-cli and have to remove the package or run yum update 'vdsm*'


Expected results:

if vdsm-cli is a depended package we should update it automatically
if we can run vdsm without vdsm-cli (since I can remove the package and just update vdsm) I do not see a reason why we should fail the vdsm update on conflict. 

Additional info:


tested with vdsm-4.9-113.4.el6_3.x86_64 ->> vdsm-4.9.6-39.0.el6_3.x86_64

Dependencies Resolved

================================================================================================================================================================================
 Package                                          Arch                               Version                                        Repository                             Size
================================================================================================================================================================================
Updating:
 vdsm                                             x86_64                             4.9.6-39.0.el6_3                               qa-latest                             675 k
Installing for dependencies:
 libvirt-lock-sanlock                             x86_64                             0.9.10-21.el6_3.5                              qa-latest                             125 k
 vdsm-python                                      x86_64                             4.9.6-39.0.el6_3                               qa-latest                              84 k

Transaction Summary
================================================================================================================================================================================
Install       2 Package(s)
Upgrade       1 Package(s)

Total download size: 884 k
Is this ok [y/N]: y
Downloading Packages:
(1/3): libvirt-lock-sanlock-0.9.10-21.el6_3.5.x86_64.rpm                                                                                                 | 125 kB     00:00     
(2/3): vdsm-4.9.6-39.0.el6_3.x86_64.rpm                                                                                                                  | 675 kB     00:00     
(3/3): vdsm-python-4.9.6-39.0.el6_3.x86_64.rpm                                                                                                           |  84 kB     00:00     
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                            25 MB/s | 884 kB     00:00     
Running rpm_check_debug
Running Transaction Test


Transaction Check Error:
  file /usr/share/vdsm/dumpStorageTable.py from install of vdsm-4.9.6-39.0.el6_3.x86_64 conflicts with file from package vdsm-cli-4.9-113.4.el6_3.x86_64
  file /usr/share/vdsm/dumpStorageTable.pyc from install of vdsm-4.9.6-39.0.el6_3.x86_64 conflicts with file from package vdsm-cli-4.9-113.4.el6_3.x86_64
  file /usr/share/vdsm/dumpStorageTable.pyo from install of vdsm-4.9.6-39.0.el6_3.x86_64 conflicts with file from package vdsm-cli-4.9-113.4.el6_3.x86_64

Comment 2 Alon Bar-Lev 2012-10-25 15:30:24 UTC
I just talked with Itamar about this.

Manual update can have conflicts. There is no problem in that. Had this been only that it was left as-is.

However as our bootstrap process of previous vdsm-bootstrap faulty and is not expected to be fixed in rhevm-3.0 engines. We should resolve the conflict <some how>

---

BTW: Dafna, it will be great if you CC discussion people from previous but to new bugs, and copy the relevant discussion.

Comment 3 Alon Bar-Lev 2012-10-25 20:03:35 UTC
commit 21b6561bb24db9c1043adac545f7d18989b7b3a2
Author: Alon Bar-Lev <alonbl>
Date:   Thu Oct 25 18:11:19 2012 +0200

    packaging: add vdsm-cli dependency to vdsm
    
    dumpStorageTable.py was moved[1][2] from vdsm-cli to vdsm package.
    
    As result when updating vdsm without vdsm-cli there is a conflict
    between the old vdsm-cli and the new vdsm packages.
    
    Our old bootstrap code which is shipped with rhevm-3.0 installs
    packages one by one, failing any bootstrap if such conflict exists.
    
    The temporary simplest solution is to pull vdsm-cli into dependency try
    of vdsm package, this dependency will be removed in future when
    newer vdsm-bootstrap be distributed to all rhevm machines.
    
    [1] Ic9dfdc2
    [2] http://gerrit.ovirt.org/1889
    
    Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=870079
    Change-Id: Ie62e19d5e1abf9c0e33b11313018a6d59640ae9c
    Signed-off-by: Alon Bar-Lev <alonbl>

diff --git a/vdsm.spec.in b/vdsm.spec.in
index 8dbe5cc..e3fe0eb 100644
--- a/vdsm.spec.in
+++ b/vdsm.spec.in
@@ -79,6 +79,12 @@ Requires: selinux-policy-targeted >= 3.7.19-80.el6
 Requires(pre,preun): policycoreutils-python
 Requires(post): /usr/sbin/saslpasswd2
 
+# backward compatible with older bootstrap code
+# see bug#870079
+# can be removed when rhevm-3.0 hosts are
+# updated with latest vdsm-bootstrap
+Requires: %{name}-cli = %{version}-%{release}
+
 %description
 The VDSM service is required by a Virtualization Manager to manage the
 Linux hosts. VDSM manages and monitors the host's storage, memory and

Comment 4 Alon Bar-Lev 2012-10-25 20:04:07 UTC
https://gerrit.eng.lab.tlv.redhat.com/#/c/2894/

Comment 5 Barak 2012-10-28 09:49:31 UTC
*** Bug 870315 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2012-12-04 19:13:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html


Note You need to log in before you can comment on or make changes to this bug.