Bug 1827067

Summary: openstack UPI: Installation leaks a server group
Product: OpenShift Container Platform Reporter: Pierre Prinetti <pprinett>
Component: InstallerAssignee: Pierre Prinetti <pprinett>
Installer sub component: OpenShift on OpenStack QA Contact: weiwei jiang <wjiang>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The Installer-assisted manifest generation creates a server group in OpenStack as a side effect. Consequence: The server group generated by the installer is ignored in UPI Fix: Reuse the same server group in UPI. Result: The server group created by the Installer is used and eventually removed on teardown by the UPI scripts.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:30:33 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:

Description Pierre Prinetti 2020-04-23 07:54:32 UTC
Description of problem:

When creating manifests, the installer creates a server group in the OpenStack cluster. That server group is not used by the UPI playbooks, and is not collected in the playbook-assisted teardown.

Comment 1 Pierre Prinetti 2020-04-23 08:42:52 UTC
This bug is a consequence on UPI of https://bugzilla.redhat.com/show_bug.cgi?id=1823487

Comment 4 Pierre Prinetti 2020-04-27 08:29:05 UTC
With the proposed fix, the UPI playbook reuses the same server group created by the Installer. This is achieved by matching the UPI server-group name with the IPI server group name.

Comment 6 errata-xmlrpc 2020-07-13 17:30:33 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.