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
I think this is a fairly easy fix. PR created: https://github.com/openshift/installer/pull/4448
Verified with 4.7.0-0.nightly-2020-12-09-040018.
Kiran, is this being backported to other releases? (that is 4.6) Thanks, Pablo
(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.
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