Bug 2007570 - [RFE] Update nodes after scale out to the latest patch level [NEEDINFO]
Summary: [RFE] Update nodes after scale out to the latest patch level
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-24 09:52 UTC by tmicheli
Modified: 2023-06-28 09:36 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
enothen: needinfo? (rhos-maint)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 843458 0 None NEW Allow operators to update package after registration 2022-05-26 13:06:56 UTC
Red Hat Issue Tracker OSP-9892 0 None None None 2021-11-18 15:02:30 UTC
Red Hat Knowledge Base (Solution) 6373081 0 None None None 2021-09-30 10:38:15 UTC

Description tmicheli 2021-09-24 09:52:49 UTC 
Description of problem:
Currently if a scale out is done,  TripleO uses the last image it has to deploy the new node and don't run any update. 
The last image usually misses all the async packages updates after images released.

I understand that from the containerized services the patch level is the same, but the underlying nodes do not have the latest patches installed. This could lead to a potential security risk if the latest ERRATA are not applied on OS level.

Currently this is only possible with doing a minor upgrade for the complete environment.

Version-Release number of selected component (if applicable):
16.y

How reproducible:


Steps to Reproduce:
1. Install an OpenStack cluster
2. Scale out
3.

Actual results:
The newly deployed compute nodes are not on the latest patch level.

Expected results:
All nodes are on the same patch level.

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