Bug 2059877 - [DOCS][Upgrade] Update RHVM update procedure in Upgrade guide
Summary: [DOCS][Upgrade] Update RHVM update procedure in Upgrade guide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.5.0-1
: 4.5.0
Assignee: Eli Marcus
QA Contact: Eli Marcus
URL:
Whiteboard: docscope 4.5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-02 09:03 UTC by Avital Pinnick
Modified: 2022-05-26 09:58 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-22 13:42:55 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44996 0 None None None 2022-03-02 09:14:36 UTC

Description Avital Pinnick 2022-03-02 09:03:49 UTC
RHEL 8.6 (GA: May 10, 2022) introduces ansible-core 2.12, making ansible-core 2.9 obsolete. ovirt-4.5 will switch to ansible-core 2.12 (GA: May 24, 2022).

To avoid a failed upgrade during the 2-week window, the `yum update` command should be changed to `yum update --nobest`. The `--nobest` option can be left in place because it will not do any harm. The link to the Kbase article on Ansible conflicts can be removed.

Section: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/upgrade_guide/index#Updating_the_Red_Hat_Virtualization_Manager_4-2_local_db (step 4)

This change affects all modules for updating RHVM.

Background: https://github.com/oVirt/ovirt-site/issues/2737#issuecomment-1054420250

Comment 1 Eli Marcus 2022-05-01 18:22:22 UTC
new PR - https://github.com/oVirt/ovirt-site/pull/2875

Comment 5 Michal Skrivanek 2022-05-02 07:00:54 UTC
hmm...I don't think it's useful o change this for 2 weeks. Especially if it may mean that without it the upgrade is failing as we do want it to fail until 4.4SP1 is out - we don't want 4.4.10 to run on RHEL 8.6 as it's not really tested that well.


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