Bug 2082054

Summary:	[RFE][OSP18] An upgraded environment and a freshly deployed environment should look the same
Product:	Red Hat OpenStack	Reporter:	Jesse Pretorius <jpretori>
Component:	RFEs	Assignee:	OSP Team <rhos-maint>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	markmc, wyahia
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.