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

CAPI: PowerVS: Use random subnet

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.16.0
    • Installer / PowerVS
    • None
    • Moderate
    • No
    • ppc64le
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when installing a cluster on {ibm-power-server-name}, the installation could fail due to a DHCP server network collision. With this update, the installation program selects a random number to generate the DHCP network to avoid collision. (link:https://issues.redhat.com/browse/OCPBUGS-33912[*OCPBUGS-33912*])
      Show
      * Previously, when installing a cluster on {ibm-power-server-name}, the installation could fail due to a DHCP server network collision. With this update, the installation program selects a random number to generate the DHCP network to avoid collision. (link: https://issues.redhat.com/browse/OCPBUGS-33912 [* OCPBUGS-33912 *])
    • Bug Fix
    • Done

      Description of problem:

      We are seeing:
      
      dhcp server failed to create private network: unable to retrieve active status for new PER connection information after create private network
      
      This error might be alleviated by not conflicting the CIDR when we create the DHCP network. One way to mitigate this is to use a random subnet address.
          

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

      
          

      How reproducible:

      Sometimes
          

      Steps to Reproduce:

          1. Create a cluster
          

      Actual results:

      
          

      Expected results:

      
          

      Additional info:

      
          

              hamzy_redhat Mark Hamzy
              hamzy_redhat Mark Hamzy
              Julie Mathew Julie Mathew
              Brendan Daly Brendan Daly
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: