Bug 1916938
Summary: | Using 4.6 install-config.yaml file with lbFloatingIP results in validation error "Forbidden: cannot specify lbFloatingIP and apiFloatingIP together" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Robert Heinzmann <rheinzma> |
Component: | Installer | Assignee: | Mike Fedosin <mfedosin> |
Installer sub component: | OpenShift on OpenStack | QA Contact: | weiwei jiang <wjiang> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | low | ||
Priority: | low | CC: | adduarte, pprinett, trees |
Version: | 4.7 | Keywords: | UpcomingSprint |
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:53:53 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
Robert Heinzmann
2021-01-15 21:50:55 UTC
The team accepts this bug as valid; we're setting LOW severity because there is an easy workaround; please advise and revert if we're wrong in the estimation. Checked with 4.7.0-0.nightly-2021-01-22-134922, and it got fixed. $ ./openshift-install-4.7 version ./openshift-install-4.7 4.7.0-0.nightly-2021-01-22-134922 built from commit d19070a771c52c9e9b3a734d3b444cfda4a575b4 release image registry.ci.openshift.org/ocp/release@sha256:cdc9ee89f08a084f51cb9e86a888b5d25a5a47ff74faf08e4067e8a3b7ceb17a # with same FIPs $ cat bz1916938/install-config.yaml | grep -i "^platform" -A 5 platform: openstack: cloud: upshift externalNetwork: provider_net_cci_8 apiFloatingIP: 10.0.100.67 lbFloatingIP: 10.0.100.67 $ ./openshift-install-4.7 create manifests --dir bz1916938 INFO Credentials loaded from file "/home/wjiang/osp_remover/clouds.yaml" INFO Consuming Install Config from target directory INFO Manifests created in: bz1916938/manifests and bz1916938/openshift # with diff FIPs: $ cat bz1916938/install-config.yaml | grep -i "^platform" -A 5 platform: openstack: cloud: upshift externalNetwork: provider_net_cci_8 apiFloatingIP: 10.0.100.67 lbFloatingIP: 10.0.99.15 $ ./openshift-install-4.7 create manifests --dir bz1916938 --log-level debug DEBUG OpenShift Installer 4.7.0-0.nightly-2021-01-22-134922 DEBUG Built from commit d19070a771c52c9e9b3a734d3b444cfda4a575b4 DEBUG Fetching Master Machines... DEBUG Loading Master Machines... DEBUG Loading Cluster ID... DEBUG Loading Install Config... DEBUG Loading SSH Key... DEBUG Loading Base Domain... DEBUG Loading Platform... DEBUG Loading Cluster Name... DEBUG Loading Base Domain... DEBUG Loading Platform... DEBUG Loading Networking... DEBUG Loading Platform... DEBUG Loading Pull Secret... DEBUG Loading Platform... FATAL failed to fetch Master Machines: failed to load asset "Install Config": failed to upconvert install config: platform.openstack.lbFloatingIP: Forbidden: cannot specify lbFloatingIP and apiFloatingIP together # with only lbFloatingIP: $ cat bz1916938/install-config.yaml | grep -i "^platform" -A 5 platform: openstack: cloud: upshift externalNetwork: provider_net_cci_8 # apiFloatingIP: 10.0.100.67 lbFloatingIP: 10.0.100.67 $ ./openshift-install-4.7 create manifests --dir bz1916938 INFO Credentials loaded from file "/home/wjiang/osp_remover/clouds.yaml" INFO Consuming Install Config from target directory INFO Manifests created in: bz1916938/manifests and bz1916938/openshift 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 |