Bug 1986083 - Rolling upgrade from 4.2 to 5.x failed during mon upgrade
Summary: Rolling upgrade from 4.2 to 5.x failed during mon upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.0z1
Assignee: Guillaume Abrioux
QA Contact: Ameena Suhani S H
Mary Frances Hull
URL:
Whiteboard:
Depends On: 1978643
Blocks: 1959686
TreeView+ depends on / blocked
 
Reported: 2021-07-26 16:09 UTC by Guillaume Abrioux
Modified: 2021-11-02 16:38 UTC (History)
14 users (show)

Fixed In Version: ceph-ansible-6.0.13-1.el8cp
Doc Type: Enhancement
Doc Text:
.Improvement to the Ceph Ansible `rolling_update.yml` playbook Previously, the Ceph Ansible `rolling_update.yml` playbook checked the Ceph version requirement of a container image later during the upgrade process. This resulted in the playbook failing in the middle of the upgrade process. With this release, the `rolling_update.yml` playbook will fail early, if the container image does not meet the Ceph version requirement.
Clone Of: 1978643
Environment:
Last Closed: 2021-11-02 16:38:27 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 6756 0 None closed update: check the ceph release (backport #6752) 2021-07-27 11:41:13 UTC
Red Hat Issue Tracker RHCEPH-1388 0 None None None 2021-09-01 03:23:47 UTC
Red Hat Product Errata RHBA-2021:4105 0 None None None 2021-11-02 16:38:56 UTC

Comment 11 errata-xmlrpc 2021-11-02 16:38: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 (Red Hat Ceph Storage 5.0 Bug Fix 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/RHBA-2021:4105
Note You need to log in before you can comment on or make changes to this bug.