Bug 1887268
| Summary: | Cannot perform yum update on my RHV manager (ansible conflict) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marcus West <mwest> |
| Component: | ovirt-engine | Assignee: | Dana <delfassy> |
| Status: | CLOSED ERRATA | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3.11 | CC: | emarcus, jortialc, lleistne, lsvaty, michal.skrivanek, mperina, paulds, pmatyas, reliezer, sergey.smirnov, swachira, usurse |
| Target Milestone: | ovirt-4.4.3 | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.4.3.8 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 13:10:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Also affecting 4.4: https://bugzilla.redhat.com/show_bug.cgi?id=1887142 workaround is to use "yum update --nobest", it doesn't affect production workloads *** Bug 1887735 has been marked as a duplicate of this bug. *** same issue with update RHV from 4.3.10 to 4.3.11 not from RHVM GUI nor from 'yum update' '--nobest' option not applicable because there is only yum available (In reply to sergey.smirnov.com from comment #5) > same issue with update RHV from 4.3.10 to 4.3.11 > not from RHVM GUI nor from 'yum update' > > '--nobest' option not applicable because there is only yum available For RHV 4.3.11 please 'yum update --exclude=ansible-2.9.14' or add 'exclude=ansible-2.9.14' into /etc/yum.conf. (In reply to Martin Perina from comment #6) > (In reply to sergey.smirnov.com from comment #5) > > same issue with update RHV from 4.3.10 to 4.3.11 > > not from RHVM GUI nor from 'yum update' > > > > '--nobest' option not applicable because there is only yum available > > For RHV 4.3.11 please 'yum update --exclude=ansible-2.9.14' or add > 'exclude=ansible-2.9.14' into /etc/yum.conf. yes, it works engine issue is targeted by BZ#1891445 docs update. for host upgrade temporary yum.conf is created by upgrade job to prevent this blockage tested on # yum list ovirt-engine Installed Packages ovirt-engine.noarch 4.4.3.9-0.1.el8ev # yum list ansible-runner-service Installed Packages ansible-runner-service.noarch 1.0.6-3.el8ev 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 (Low: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5179 *** Bug 1920407 has been marked as a duplicate of this bug. *** |
## Description of problem: When trying to yum update RHVM instance, I get an error regarding and ansible conflict ## Version-Release number of selected component (if applicable): ovirt-engine-4.3.11.4-0.1.el7.noarch ## How reproducible: Always ## Steps to Reproduce: 1. Update RHVM manager to 4.3.11 2. run 'yum update' on RHVM manager ## Actual results: Dependency error: ~~~ # yum update Loaded plugins: enabled_repos_upload, package_upload, product-id, search-disabled-repos, subscription-manager, : tracer_upload, versionlock rhel-7-server-ansible-2.9-rpms | 2.3 kB 00:00:00 rhel-7-server-rh-common-rpms | 2.1 kB 00:00:00 rhel-7-server-rhv-4-manager-tools-rpms | 2.3 kB 00:00:00 rhel-7-server-rhv-4.3-manager-rpms | 2.4 kB 00:00:00 rhel-7-server-rpms | 2.0 kB 00:00:00 rhel-7-server-supplementary-rpms | 2.0 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package ansible.noarch 0:2.9.13-1.el7ae will be updated --> Processing Dependency: ansible = 2.9.13 for package: ovirt-engine-4.3.11.4-0.1.el7.noarch ---> Package ansible.noarch 0:2.9.14-1.el7ae will be an update --> Finished Dependency Resolution Error: Package: ovirt-engine-4.3.11.4-0.1.el7.noarch (@rhel-7-server-rhv-4.3-manager-rpms) Requires: ansible = 2.9.13 Removing: ansible-2.9.13-1.el7ae.noarch (@rhel-7-server-ansible-2-rpms) ansible = 2.9.13-1.el7ae Updated By: ansible-2.9.14-1.el7ae.noarch (rhel-7-server-ansible-2.9-rpms) ansible = 2.9.14-1.el7ae ~~~ ## Expected results: RHV Manager should update without error ## Additional info: This happens for both the 'rhel-7-server-ansible-2.9-rpms' and 'rhel-7-server-ansible-2-rpms' channels RHEL hosts being used as hypervisors apparently have the same issue: (with ovirt-hosted-engine-setup) ~~~ --> Running transaction check ---> Package ansible.noarch 0:2.9.13-1.el7ae will be updated --> Processing Dependency: ansible = 2.9.13 for package: ovirt-hosted-engine-setup-2.3.13-2.el7ev.noarch ---> Package bc.x86_64 0:1.06.95-13.el7 will be installed ---> Package ovirt-hosted-engine-setup.noarch 0:2.3.13-2.el7ev will be an update --> Processing Dependency: ansible = 2.9.13 for package: ovirt-hosted-engine-setup-2.3.13-2.el7ev.noarch --> Finished Dependency Resolution Error: Package: ovirt-hosted-engine-setup-2.3.13-2.el7ev.noarch (rhel-7-server-rhv-4-mgmt-agent-rpms) Requires: ansible = 2.9.13 Removing: ansible-2.9.13-1.el7ae.noarch (@rhel-7-server-ansible-2-rpms) ansible = 2.9.13-1.el7ae Updated By: ansible-2.9.14-1.el7ae.noarch (rhel-7-server-ansible-2.9-rpms) ansible = 2.9.14-1.el7ae ~~~