Bug 1613438
| Summary: | OpenShift on OpenStack Ansible Installer creates CNS security group when openshift_openstack_num_cns is set to zero | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | rlopez |
| Component: | Installer | Assignee: | aos-install |
| Installer sub component: | openshift-installer | QA Contact: | Gaoyun Pei <gpei> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aos-bugs, gcheresh, jokerman, mmccomas, rlopez, tzumainn, vrutkovs, wsun |
| Version: | 3.10.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 3.11 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: The Openshift Ansible Installer did not check if any CNS are created before creating a security group.
Consequence: It would create a security group for CNS even when there were none created.
Fix: The Openshift Ansible Installer checks that openshift_openstack_num_cns is greater than zero before creating a security group for CNS.
Result: CNS security groups are only created when there is at least one CNS created
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-10 09:03:58 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: | |||
|
Description
rlopez
2018-08-07 14:28:05 UTC
3.11 cherrypick - https://github.com/openshift/openshift-ansible/pull/10391 Fix is available in openshift-ansible-3.11.23-1 A patch has been merged. Please help check if this bug could be verified,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, 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-2019:0024 |