Bug 2090442 - [Cephadm] Document Staggered Upgrade
Summary: [Cephadm] Document Staggered Upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2
Assignee: ceph-docs@redhat.com
QA Contact: Manasa
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-25 18:43 UTC by Vikhyat Umrao
Modified: 2023-09-15 01:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 14:21:15 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2016936 1 unspecified CLOSED [RFE] Support for staggered/control upgrade of ceph nodes by role, hosts/rack 2022-08-09 17:43:10 UTC
Red Hat Issue Tracker RHCEPH-3703 0 None None None 2022-05-25 18:55:44 UTC
Red Hat Issue Tracker RHCEPH-4387 0 None None None 2022-05-25 18:48:59 UTC

Internal Links: 2016936

Description Vikhyat Umrao 2022-05-25 18:43:17 UTC
Describe the issue:
[Cephadm] Document Staggered Upgrade

See for more details:
https://bugzilla.redhat.com/show_bug.cgi?id=2016936#c6
Some documentation on this can be found at https://docs.ceph.com/en/quincy/cephadm/upgrade/#staggered-upgrade. For QE, since this is the first version we are adding this, you will need to follow the workaround described in https://docs.ceph.com/en/quincy/cephadm/upgrade/#upgrading-to-a-version-that-supports-staggered-upgrade-from-one-that-doesn-t.


Describe the task you were trying to accomplish:

Suggestions for improvement: update the upgrade section in the installation guide

This needs to be documented in the installation/upgrade guide in RHCS 5.2 and above!

Comment 7 Red Hat Bugzilla 2023-09-15 01:55:12 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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