• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.19.0
    • Installer / PowerVS
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, an {ibm-power-server-name} cluster installation failed on installer-provisioned infrastructure because the installation program used a random network type instead of using of the specified network type that was specified in the `install-config.yaml` configuration file. With this release, the installation program now uses the network type that is specified in the `install-config.yaml` so that this issue no longer persists. (link:https://issues.redhat.com/browse/OCPBUGS-45484[*OCPBUGS-45484*])
      Show
      * Previously, an {ibm-power-server-name} cluster installation failed on installer-provisioned infrastructure because the installation program used a random network type instead of using of the specified network type that was specified in the `install-config.yaml` configuration file. With this release, the installation program now uses the network type that is specified in the `install-config.yaml` so that this issue no longer persists. (link: https://issues.redhat.com/browse/OCPBUGS-45484 [* OCPBUGS-45484 *])
    • Bug Fix
    • Done

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

      Description of problem:

      For Power VS installs, previously the installer would use a random network instead of using the one specified in the install config. With this release, the installer will now use the machine network specified in the install config, or a default network.

            [OCPBUGS-45484] PowerVS: Listen to machineNetwork

            Swapnil Bobade added a comment - - edited

            4.17 IPI cluster deploy successful with-

             machineNetwork:
            - cidr: 192.168.0.0/24 
            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/home/cloudusr/ipi/417/osa21/auth/kubeconfig'
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-bug45484-417.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "**************"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 9m26s
            DEBUG Post-network, pre-machine Provisioning: 25s
            DEBUG                   Machine Provisioning: 10m0s
            DEBUG       Infrastructure Post-provisioning: 1m18s
            DEBUG                     Bootstrap Complete: 44m50s
            DEBUG                                    API: 6m17s
            DEBUG                      Bootstrap Destroy: 2m34s
            DEBUG            Cluster Operators Available: 31m14s
            DEBUG               Cluster Operators Stable: 2m53s
            INFO Time elapsed: 1h43m28s 

             

            Also, tried with Multiple machinenetwork

              machineNetwork:
              - cidr: 192.168.0.0/24
              - cidr: 192.168.15.0/24 

            got successful deploy

            INFO Install complete!
            INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/home/cloudusr/ipi/417/osa21/auth/kubeconfig'
            INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ipi-417-bug45484-osa21.qe-ppc64le.cis.ibm.net
            INFO Login to the console with user: "kubeadmin", and password: "**********"
            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 9m11s
            DEBUG Post-network, pre-machine Provisioning: 26s
            DEBUG                   Machine Provisioning: 9m0s
            DEBUG       Infrastructure Post-provisioning: 1m25s
            DEBUG                     Bootstrap Complete: 42m40s
            DEBUG                                    API: 9m8s
            DEBUG                      Bootstrap Destroy: 11s
            DEBUG            Cluster Operators Available: 29m53s
            DEBUG               Cluster Operators Stable: 48s
            INFO Time elapsed: 1h34m18s 

             

            logs uploaded - here

            Swapnil Bobade added a comment - - edited 4.17 IPI cluster deploy successful with- machineNetwork: - cidr: 192.168.0.0/24 INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run 'export KUBECONFIG=/home/cloudusr/ipi/417/osa21/auth/kubeconfig' INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-bug45484-417.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "**************" DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 9m26s DEBUG Post-network, pre-machine Provisioning: 25s DEBUG                   Machine Provisioning: 10m0s DEBUG       Infrastructure Post-provisioning: 1m18s DEBUG                     Bootstrap Complete: 44m50s DEBUG                                    API: 6m17s DEBUG                      Bootstrap Destroy: 2m34s DEBUG            Cluster Operators Available: 31m14s DEBUG               Cluster Operators Stable: 2m53s INFO Time elapsed: 1h43m28s   Also, tried with Multiple machinenetwork machineNetwork: - cidr: 192.168.0.0/24 - cidr: 192.168.15.0/24 got successful deploy INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc' , run 'export KUBECONFIG=/home/cloudusr/ipi/417/osa21/auth/kubeconfig' INFO Access the OpenShift web-console here: https: //console-openshift-console.apps.ipi-417-bug45484-osa21.qe-ppc64le.cis.ibm.net INFO Login to the console with user: "kubeadmin" , and password: "**********" DEBUG Time elapsed per stage: DEBUG Network-infrastructure Provisioning: 9m11s DEBUG Post-network, pre-machine Provisioning: 26s DEBUG Machine Provisioning: 9m0s DEBUG Infrastructure Post-provisioning: 1m25s DEBUG Bootstrap Complete: 42m40s DEBUG API: 9m8s DEBUG Bootstrap Destroy: 11s DEBUG Cluster Operators Available: 29m53s DEBUG Cluster Operators Stable: 48s INFO Time elapsed: 1h34m18s   logs uploaded - here

            Wei Sun added a comment -

            jmathew@redhat.com Please check if this bug could be verified, thanks!

            Wei Sun added a comment - jmathew@redhat.com Please check if this bug could be verified, thanks!

              mturek.coreos Michael Turek
              openshift-crt-jira-prow OpenShift Prow Bot
              Julie Mathew Julie Mathew (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: