Bug 1904125

Summary:	Boostrap VM .ign image gets added into 'default' pool instead of <cluster-name>-<id>-bootstrap
Product:	OpenShift Container Platform	Reporter:	rlopez
Component:	Installer	Assignee:	Kiran Thyagaraja <kiran>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Ori Michaeli <omichael>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	kiran, pablo.iranzo, rbartal
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.7.0
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:	2021-02-24 15:37:28 UTC	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:
Bug Depends On:
Bug Blocks:	1831748

Description rlopez 2020-12-03 15:41:40 UTC

Currently with working with OCP 4.6 or higher, during IPI installs the bootstrap VM creates two volumes <clustername>-<id>-bootstrap and <clustername>-<id>-boostrap.ign

If an existing pool labeled default already exists, the .ign volume always gets created within the default pool while the <clustername>-<id>-boostrap volume, gets created in a new pool labeled '<clustername>-<id>-boostrap'.

The solution should be that both volumes .ign and regular bootstrap volume should reside within the <clustername>-<id>-boostrap pool not a default pool (if it already exists).

This will make installs easier to clean up as everything related to the bootstrap VM and the IPI installs would be in its appropriate pool.

100% Reproducible

Comment 1 Kiran Thyagaraja 2020-12-03 16:46:47 UTC

I think this is a fairly easy fix. PR created: https://github.com/openshift/installer/pull/4448

Comment 4 Ori Michaeli 2020-12-09 13:00:31 UTC

Verified with 4.7.0-0.nightly-2020-12-09-040018.

Comment 5 Pablo Iranzo Gómez 2020-12-15 14:11:31 UTC

Kiran, is this being backported to other releases? (that is 4.6)

Thanks,
Pablo

Comment 6 Kiran Thyagaraja 2020-12-16 14:51:16 UTC

(In reply to Pablo Iranzo Gómez from comment #5)
> Kiran, is this being backported to other releases? (that is 4.6)
> 
> Thanks,
> Pablo

Hi Pablo, As of now, there are no plans, but I'll update the BZ if we create a backport. Thanks.

Comment 9 errata-xmlrpc 2021-02-24 15:37:28 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633