Dear all, when installing OpenShift Container Platform 4.2 on OpenStack, the installer exits hard with the following error: ~~~ $ ./openshift-install create ignition-configs --dir=foo --log-level=debug DEBUG OpenShift Installer v4.2.13 DEBUG Built from commit 46f909e4ccb4f7a4f82bf1ee28b32fa011a6bd1f DEBUG Fetching "Kubeconfig Admin Client"... DEBUG Loading "Kubeconfig Admin Client"... DEBUG Loading "Certificate (admin-kubeconfig-client)"... DEBUG Loading "Certificate (admin-kubeconfig-signer)"... DEBUG Loading "Certificate (kube-apiserver-complete-server-ca-bundle)"... DEBUG Loading "Certificate (kube-apiserver-localhost-ca-bundle)"... DEBUG Loading "Certificate (kube-apiserver-localhost-signer)"... DEBUG Loading "Certificate (kube-apiserver-service-network-ca-bundle)"... DEBUG Loading "Certificate (kube-apiserver-service-network-signer)"... DEBUG Loading "Certificate (kube-apiserver-lb-ca-bundle)"... DEBUG Loading "Certificate (kube-apiserver-lb-signer)"... 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 "Pull Secret"... DEBUG Loading "Platform"... FATAL failed to fetch Kubeconfig Admin Client: failed to load asset "Install Config": invalid "install-config.yaml" file: platform.openstack.trunkSupport: Internal error: could not retrieve networking extension aliases ~~~ We can see that this fails because the installer can't contact the necessary OpenStack endpoints: ~~~ $ openstack extension list --os-cloud otc Extensions list not supported by Identity API Extensions list not supported by Compute API Failed to retrieve extensions list from Network API ~~~ Can we possibly make the installer show a warning when it can't check for trunks and for octavia as opposed to exiting hard?
Please, note that OCP 4.2 has only been tested and is supported on OSP 13 and OSP 15.
Verified on 4.4.0-0.nightly-2020-02-18-140650
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-2020:0581
*** Bug 1830357 has been marked as a duplicate of this bug. ***