Thanks for opening a bug report! Before hitting the button, please fill in as much of the template below as you can. If you leave out information, it's harder to help you. Be ready for follow-up questions, and please respond in a timely manner. If we can't reproduce a bug we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. Version: $ openshift-install version <your output here> Platform: #Power VS Please specify: * IPI (automated install with `openshift-install`. If you don't know, then it's IPI) What happened? #Generating Manifests failed with UAAEndpoint not found error Error:FATAL failed to fetch Master Machines: failed to fetch dependency of "Master Machines": failed to generate asset "Platform Credentials Check": ServiceEndpointDoesnotExist: UAA endpoint doesn't exist for region: "jp-osa"`] Expected: Manifests should be generated successfully. #See the troubleshooting documentation (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md) for ideas about what information to collect. #For example, # If the installer fails to create resources (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-create-resources), attach the relevant portions of your `.openshift_install.log.` # If the installer fails to bootstrap the cluster (https://github.com/openshift/installer/blob/master/docs/user/troubleshootingbootstrap.md), attach the bootstrap log bundle. # If the installer fails to complete installation after bootstrapping completes (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-initialize-the-cluster), attach the must-gather log bundle using `oc adm must-gather` # Always at least include the `.openshift_install.log` What did you expect to happen? #Enter text here. How to reproduce it (as minimally and precisely as possible)? $ your-commands-here Anything else we need to know? #Enter text here.
Issue is reproduced with the latest available build in mirror repo. https://mirror.openshift.com/pub/openshift-v4/ppc64le/clients/ocp-dev-preview/4.11.0-0.nightly-ppc64le-2022-06-16-003709/ Will wait for the next nightly build to re-test and verify this bug.
Verified with a new 4.11 nightly build '4.11.0-0.nightly-ppc64le-2022-06-21-133338'. Support for region: jp-osa works as expected. [root@mjul-rhl85-x1 june22]# ./openshift-install create install-config --dir 411-06-21 ? SSH Public Key /root/.ssh/id_rsa.pub ? Platform powervs ? IBM Cloud User ID mjulie.com ? IBM Cloud API Key [? for help] ******************************************** ? Region osa ? Zone osa21 ? Base Domain ocp-powervs-ppc64le.com (rdr-ipi-validation-dns) ? Cluster Name rdr-mjulie-june21 ? Pull Secret [? for help] ******************** INFO Install-Config created in: 411-06-21 [root@mjul-rhl85-x1 june22]# ./openshift-install create manifests --dir 411-06-21 INFO Consuming Install Config from target directory INFO Manifests created in: 411-06-21/manifests and 411-06-21/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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069