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

Metal3 / BMO ignores setting in install-config and sets wrong BMC address to wrong machine in ABI installs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Undefined Undefined
    • None
    • 4.16
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When installing a bare metal cluster with ABI,
      Setting the CR provisioning/provisioning-configuration, where you remove all values and setting provisioningNetwork: Disabled -  metal3 / BMO sets the wrong machine on the wrong bmh.    

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

      4.16.9    

      How reproducible:

      Very    

      Steps to Reproduce:

          1. add control-plane nodes with custom network config in agent-config.yaml, but omit any provisioningNetwork settings in install-config.
          2. install cluster and see that baremetal operator is not progressing.
          3. change provisioningNetwork: to Disabled in provisioning CR.
          4. Observe machineset machines get the wrong PROVIDER ID attached to them.
          

      Actual results:

          wrong provider id attached to machines in machineset

      Expected results:

          correct providerid to correct node for each machine in cluster.

      Additional info:

          Some logs and cli logs attached.

              rhn-engineering-dtantsur Dmitry Tantsur
              jnaess@redhat.com Jørgen Ness
              Jad Haj Yahya Jad Haj Yahya
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: