Red Hat Bugzilla – Bug 1276511
[Docs] [Upgrade] Provide further clarification of the upgrade scenarios
Last modified: 2016-01-17 18:23:39 EST
Description of problem: Document located here:
The abstract states:
This document lays out the different methods through which users can upgrade from Red Hat Enterprise Linux OpenStack Platform 6 (Juno) to 7 (Kilo). These methods assume that you will be upgrading to and from an OpenStack deployment installed on Red Hat Enterprise Linux 7.
But the document is clearly for upgrading 7.0 -> 7.1
The abstract needs to be udpated
Version-Release number of selected component (if applicable): 7
How reproducible: 100%
Steps to Reproduce:
1. Pull up the Access article and read the abstract
Abstract claims upgrade from 6->7
Abstract states upgrade from 7->7.1
Thank you for raising this bug.
Just to clarify, the intent of this document is indeed to assist users in upgrading from RHEL-OSP 6 to RHEL-OSP 7 rather than from RHEL-OSP 7.0 to RHEL-OSP 7.1.
Are there any particular aspects of the document that you feel do not fit with this scenario, or that may seem misleading to the reader?
Let me know what you think, and we will investigate.
I reviewed chapter 3 which appears to be specific to 7->7.1 it looks like chapter 4 applies to 6->7 Can you confirm this?
Thank you for your response.
I can confirm that Chapter 3 is also intended as an upgrade path from RHEL-OSP 6 to RHEL-OSP 7. However, I do agree that the note early in this chapter about the possibly need to upgrade from RHEL 7.0 to RHEL 7.1 might be a point of confusion here.
Would it help if we called out the purpose of the scenario a little more clearly at the start of the chapter and talked a little more about the RHEL upgrade as well?
Let me know what you think.
That would be great!
Assigning to Deepti for review.
Deepti - would you be able to add some clarification as per the comments above? Let me know if you have any questions.
Sent an email reminder to Arthur for update review.
Content merged. Changing status to VERIFIED.
This content is live on the Customer Portal.