Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-47663

Power VS: Available SysTypes should be decided by zone rather than region

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.16.z
    • 4.17.z
    • Installer / PowerVS
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, you could not use all the available machine types in a zone for a clsuter installed on {ibm-power-server-name}. This issues existed because all zones in a region were assumed to have the same set of machine types. With this release, you can use all the available machine types in a zone for a clsuter installed on {ibm-power-server-name}. (link:https://issues.redhat.com/browse/OCPBUGS-47663[*OCPBUGS-47663*])
      Show
      * Previously, you could not use all the available machine types in a zone for a clsuter installed on {ibm-power-server-name}. This issues existed because all zones in a region were assumed to have the same set of machine types. With this release, you can use all the available machine types in a zone for a clsuter installed on {ibm-power-server-name}. (link: https://issues.redhat.com/browse/OCPBUGS-47663 [* OCPBUGS-47663 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-46432. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-45685. The following is the description of the original issue:

      Description of problem:

      As more systems have been added to Power VS, the assumption that every zone in a region has the same set of systypes has been broken. To properly represent what system types are available, the powervs_regions struct needed to be altered and parts of the installer referencing it needed to be updated.

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          

      Steps to Reproduce:

      1. Try to deploy with s1022 in dal10
      2. SysType not available, even though it is a valid option in Power VS.     

      Actual results:

          

      Expected results:

          

      Additional info:

          

            [OCPBUGS-47663] Power VS: Available SysTypes should be decided by zone rather than region

            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.16.32 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-2025:0650

            Errata Tool added a comment - 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.16.32 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-2025:0650

            Moved to Proposed

            OpenShift Jira Bot added a comment - Moved to Proposed

            Hi mturek.coreos,

            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 mturek.coreos , 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.

              mturek.coreos Michael Turek
              openshift-crt-jira-prow OpenShift Prow Bot
              Julie Mathew Julie Mathew
              Ashwin Hendre
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: