Bug 2082054 - [RFE][OSP18] An upgraded environment and a freshly deployed environment should look the same
Summary: [RFE][OSP18] An upgraded environment and a freshly deployed environment shoul...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 10:24 UTC by Jesse Pretorius
Modified: 2022-05-05 11:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-15054 0 None None None 2022-05-05 10:52:03 UTC

Description Jesse Pretorius 2022-05-05 10:24:58 UTC
In order to reduce operational problems once an environment is upgraded, and to ensure like-for-like functional parity, an environment which has been upgraded and a freshly deployed environment should look the same from the following points of view:

1. Package versions installed on the host
2. The packages installed on the host
2. Container versions present on the host

The same should be true for a scaled-up new host in an environment that is freshly deployed or scaled up.

If there are any deviations from this pattern, they should be clearly noted in the documentation with the rationale behind the difference.

Currently it is required to run the update process on a scaled-up node in order to ensure that the node is up to date. This extends the time taken considerably.


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