Bug 1816092

Summary:	[UPI on OSP] Machine-controller cannot create workers required by machineset because it is not using the same RHCOS image name
Product:	OpenShift Container Platform	Reporter:	Pierre Prinetti <pprinett>
Component:	Installer	Assignee:	Pierre Prinetti <pprinett>
Installer sub component:	OpenShift on OpenStack	QA Contact:	David Sanz <dsanzmor>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	dsanzmor, pprinett
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Steps for using the default machineset with UPI are not documented Consequence: scale-out is not available out-of-the-box Fix: Document the steps for using the machineset created by the installer Result: scale-out is available if following the documented steps	Story Points:	---
Clone Of:	1815133	Environment:
Last Closed:	2020-05-13 22:01:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1815133
Bug Blocks:

Description Pierre Prinetti 2020-03-23 10:44:02 UTC

+++ This bug was initially created as a clone of Bug #1815133 +++

Description of problem:

When installing UPI on OSP, RHCOS image is preloaded on OSP and identified by os_image_rhcos parameter in the inventory.

Machineset is using another name for the image, and it cannot create workers

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


How reproducible:


Steps to Reproduce:
1.Install UPI on OSP
2.Try to scale workers using the machineset
3.Watch logs of machine-controller: oc logs -f pod/machine-api-controllers-xxxxxx -c machine-controller

Actual results:
Machine-controller cannot create workers

Expected results:
machine-controller use the same image than the installer

Additional info:

Comment 4 David Sanz 2020-04-02 11:33:44 UTC

Verified as change is only related to docs

Comment 6 errata-xmlrpc 2020-05-13 22:01:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581