Description of problem:
IPI on IBM Cloud does not currently support the new eu-es region
Version-Release number of selected component (if applicable):
4.15
How reproducible:
100%
Steps to Reproduce:
1. Create install-config.yaml for IBM Cloud, per docs, using eu-es region 2. Create the manifests (or cluster) using IPI
Actual results:
level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: platform.ibmcloud.region: Unsupported value: "eu-es": supported values: "us-south", "us-east", "jp-tok", "jp-osa", "au-syd", "ca-tor", "eu-gb", "eu-de", "br-sao"
Expected results:
Successful IBM Cloud OCP cluster in eu-es
Additional info:
IBM Cloud has started testing a potential fix, in eu-es to confirm supported cluster types (Public, Private, BYON) all work properly in eu-es
- blocks
-
OCPBUGS-22978 [IBMCloud] Add IPI support for new region eu-es (Madrid)
-
- Closed
-
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is documented by
-
-
- Closed
-
- links to
-
RHBA-2024:0941
OpenShift Container Platform 4.14.z bug fix update
-
RHEA-2023:7198
rpm
[OCPBUGS-19398] [IBMCloud] Add IPI support for new region eu-es (Madrid)
kalexand@redhat.com
Cause: New region eu-es is supported by IBMCloud VPC
Consequence: Can not install cluster on IBMCloud VPC eu-es region
Fix: install cluster on IBMCloud VPC eu-es region
Result: Bug doesn’t present anymore.
The docs team is preparing the bug text for the 4.15 release notes. Based on the fix and affects version, this bug needs to be included in the release notes. Please update your issue by 2/12.
Set the Release Note Type to Bug Fix and provide the Release Note Text in the following format:
Cause: What actions or circumstances cause this bug to present.
Consequence: What happens when the bug presents.
Fix: What was done to fix the bug.
Result: Bug doesn’t present anymore.
If your bug was actually found and fixed in 4.15 or should be internal only, set the Release Note Type to Release Note Not Required.
OpenShift Jira Bot
added a comment - Hi jeffbnowicki,
Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.
OpenShift Jira Bot
added a comment - Hi jeffbnowicki ,
Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified. pre-merge check pass, build info [ merging: #7668 cd46f90f] (https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-launch-aws-modern/1719904454012047360/build-log.txt)
create a vpc cluster succeed.
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.14.14 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-2024:0941