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

Power VS: Add new regions that have added PER capabilities

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.18.0
    • Installer / PowerVS
    • None
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, US East (`wdc04`), US South (`dal13`), Sydney (`syd05`), and Toronto (`tor01`) regions were not supported for {ibm-power-server-title}. With this release, these regions, which include `PowerEdgeRouter` (PER) capabilities, are supported for {ibm-power-server-title}.
      (link:https://issues.redhat.com/browse/OCPBUGS-44312[*OCPBUGS-44312*])
      Show
      * Previously, US East (`wdc04`), US South (`dal13`), Sydney (`syd05`), and Toronto (`tor01`) regions were not supported for {ibm-power-server-title}. With this release, these regions, which include `PowerEdgeRouter` (PER) capabilities, are supported for {ibm-power-server-title}. (link: https://issues.redhat.com/browse/OCPBUGS-44312 [* OCPBUGS-44312 *])
    • Proposed

      Description of problem:

      There are four additional zones, syd05, us-east(wdc04), us-south(dal13) and tor01 that have PER capabilities but are not present in the installer. Add them.    

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

      4.18.0    

            [OCPBUGS-44312] Power VS: Add new regions that have added PER capabilities

            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.18.1 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:6122

            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.18.1 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:6122

            us-south -

            IPI deployment is successful using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build

            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run
            INFO     export KUBECONFIG=/home/cloudusr/ipi/418/ussouth/auth/kubeconfig
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-418-us-south.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "*****************"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 19m11s
            DEBUG Post-network, pre-machine Provisioning: 24s
            DEBUG                   Machine Provisioning: 7m30s
            DEBUG       Infrastructure Post-provisioning: 1m10s
            DEBUG                     Bootstrap Complete: 31m8s
            DEBUG                                    API: 6m1s
            DEBUG                      Bootstrap Destroy: 31s
            DEBUG            Cluster Operators Available: 25m48s
            DEBUG               Cluster Operators Stable: 52s
            DEBUG                                Console: 1s
            INFO Time elapsed: 1h27m18s
             

            Install log uploaded - here

            Swapnil Bobade added a comment - us-south - IPI deployment is successful using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run INFO     export KUBECONFIG=/home/cloudusr/ipi/418/ussouth/auth/kubeconfig INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-418-us-south.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "*****************" DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 19m11s DEBUG Post-network, pre-machine Provisioning: 24s DEBUG                   Machine Provisioning: 7m30s DEBUG       Infrastructure Post-provisioning: 1m10s DEBUG                     Bootstrap Complete: 31m8s DEBUG                                    API: 6m1s DEBUG                      Bootstrap Destroy: 31s DEBUG            Cluster Operators Available: 25m48s DEBUG               Cluster Operators Stable: 52s DEBUG                                Console: 1s INFO Time elapsed: 1h27m18s Install log uploaded - here

            Swapnil Bobade added a comment - - edited

            tor01 -

            IPI deployment is successful using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build{}

            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run
            INFO     export KUBECONFIG=/home/cloudusr/ipi/418/tor01/auth/kubeconfig
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-418-tor01.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "*************"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 7m25s
            DEBUG Post-network, pre-machine Provisioning: 21s
            DEBUG                   Machine Provisioning: 6m15s
            DEBUG       Infrastructure Post-provisioning: 1m22s
            DEBUG                     Bootstrap Complete: 30m22s
            DEBUG                                    API: 5m49s
            DEBUG                      Bootstrap Destroy: 31s
            DEBUG            Cluster Operators Available: 25m1s
            DEBUG               Cluster Operators Stable: 46s
            INFO Time elapsed: 1h12m50s 

            Install log uploaded - here

            Swapnil Bobade added a comment - - edited tor01 - IPI deployment is successful using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build { } INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run INFO     export KUBECONFIG=/home/cloudusr/ipi/418/tor01/auth/kubeconfig INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-418-tor01.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "*************" DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 7m25s DEBUG Post-network, pre-machine Provisioning: 21s DEBUG                   Machine Provisioning: 6m15s DEBUG       Infrastructure Post-provisioning: 1m22s DEBUG                     Bootstrap Complete: 30m22s DEBUG                                    API: 5m49s DEBUG                      Bootstrap Destroy: 31s DEBUG            Cluster Operators Available: 25m1s DEBUG               Cluster Operators Stable: 46s INFO Time elapsed: 1h12m50s Install log uploaded - here

            Swapnil Bobade added a comment - - edited

            IPI cluster deployment is successful on us-east using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build 

            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run
            INFO     export KUBECONFIG=/home/cloudusr/ipi/418/useast/auth/kubeconfig
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-418-nig-useast.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "*******************"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 9m25s
            DEBUG Post-network, pre-machine Provisioning: 24s
            DEBUG                   Machine Provisioning: 8m45s
            DEBUG       Infrastructure Post-provisioning: 1m12s
            DEBUG                     Bootstrap Complete: 33m20s
            DEBUG                                    API: 7m15s
            DEBUG                      Bootstrap Destroy: 55s
            DEBUG            Cluster Operators Available: 23m2s
            DEBUG               Cluster Operators Stable: 48s
            INFO Time elapsed: 1h18m33s
             

            Install logs uploaded - here

            Swapnil Bobade added a comment - - edited IPI cluster deployment is successful on us-east using 4.18.0-0.nightly-ppc64le-2025-01-13-052235 build   INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run INFO     export KUBECONFIG=/home/cloudusr/ipi/418/useast/auth/kubeconfig INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-418-nig-useast.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "*******************" DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 9m25s DEBUG Post-network, pre-machine Provisioning: 24s DEBUG                   Machine Provisioning: 8m45s DEBUG       Infrastructure Post-provisioning: 1m12s DEBUG                     Bootstrap Complete: 33m20s DEBUG                                    API: 7m15s DEBUG                      Bootstrap Destroy: 55s DEBUG            Cluster Operators Available: 23m2s DEBUG               Cluster Operators Stable: 48s INFO Time elapsed: 1h18m33s Install logs uploaded - here

            IPI cluster deployment is successful on syd05 using 4.18.0-0.nightly-ppc64le-2025-01-09-031005 build 

            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run
            INFO     export KUBECONFIG=/home/cloudusr/ipi/418/syd05/auth/kubeconfig
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-418nig-syd05.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "******************"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 8m55s
            DEBUG Post-network, pre-machine Provisioning: 30s
            DEBUG                   Machine Provisioning: 6m45s
            DEBUG       Infrastructure Post-provisioning: 1m29s
            DEBUG                     Bootstrap Complete: 36m22s
            DEBUG                                    API: 7m2s
            DEBUG                      Bootstrap Destroy: 56s
            DEBUG            Cluster Operators Available: 26m19s
            DEBUG               Cluster Operators Stable: 45s
            INFO Time elapsed: 1h22m50s
             

            Install log uploaded - here

            Swapnil Bobade added a comment - IPI cluster deployment is successful on syd05 using 4.18.0-0.nightly-ppc64le-2025-01-09-031005 build   INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run INFO     export KUBECONFIG=/home/cloudusr/ipi/418/syd05/auth/kubeconfig INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-418nig-syd05.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "******************" DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 8m55s DEBUG Post-network, pre-machine Provisioning: 30s DEBUG                   Machine Provisioning: 6m45s DEBUG       Infrastructure Post-provisioning: 1m29s DEBUG                     Bootstrap Complete: 36m22s DEBUG                                    API: 7m2s DEBUG                      Bootstrap Destroy: 56s DEBUG            Cluster Operators Available: 26m19s DEBUG               Cluster Operators Stable: 45s INFO Time elapsed: 1h22m50s Install log uploaded - here

            Hi ahendre2,

            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 ahendre2 , 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.

              ahendre2 Ashwin Hendre
              ahendre2 Ashwin Hendre
              Julie Mathew Julie Mathew
              Ashwin Hendre
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: