Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358009 - [ceph-ansible] - '5.4. UPGRADING FROM TRUSTY TO XENIAL ' - needs modification as it does not upgrade cluster node by node but makes cluster offline
Summary: [ceph-ansible] - '5.4. UPGRADING FROM TRUSTY TO XENIAL ' - needs modification...
Keywords:
Status: CLOSED DUPLICATE of bug 1357948
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: documentation
Version: 2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 2
Assignee: Anjana Suparna Sriram
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-19 20:04 UTC by Rachana Patel
Modified: 2016-07-28 16:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-28 16:14:47 UTC


Attachments (Terms of Use)

Description Rachana Patel 2016-07-19 20:04:09 UTC
Description of problem:
========================
 '5.4. UPGRADING FROM TRUSTY TO XENIAL '  needs modification

Usually we should upgrade cluster one node after other but if we follow instruction mentioned in this section we end up taking cluster offline by killing all ceph processes on all node while execution step c.

detail:-

Under 5.4

1.Upgrade the Red Hat Ceph Storage packages
a. disable repo...
b. enable repo..

Now step c says:-

Stop the running Ceph daemons:
Monitor nodes:
OSD nodes:
RADOS Gateway nodes:

Step D ask to upgrade package etc.

If we follow this Document, cluster would be offline


How reproducible:
================
always



Expected results:
===================
Like RHEL upgrade doc, it should clearly mentioned that do upgrade node by node and even steps should be arranged in similar way.
e.g.
1. steps to upgrade mon
mention that upgrade mon one by one and when all mon are upgraded move to ODS
2. steps to upgrade OSD
mention that upgrade OSD one by one and when all osds are upgraded move to clients etc.
3. steps to upgrade client.
..
..


Additional info:


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