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

Static networking is not applicable using config-image API

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • No
    • None
    • None
    • Rejected
    • Sprint 239
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When creating a config-image, static network should be configured using hosts property on agent-config.yaml.
      But the following error is thrown from service: "nmstateconfig should have at least one label set matching the infra-env label selector".

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

      4.14

      How reproducible:

      100%

      Steps to Reproduce:

      1. Add 'hosts' to agent-config.yaml (for configuring static networking)
      2. Run 'agent create config-image'
      3. Mount ISO to machine
      

      Actual results:

      The cluster installation won't start due to:
      "nmstateconfig should have at least one label set matching the infra-env label selector"

      Expected results:

      The cluster installation should start.

      Additional info:

      A workaround for the issue is to add 'nmStateConfigLabelSelector' in the infraenv.yaml provided to unconfigured-ignition API. However, as we don't know the cluster name/namespace in this stage, it can't be supplied yet. Hence, it should be generated as part of the config-image.

              bfournie@redhat.com Robert Fournier
              derez@redhat.com Daniel Erez
              None
              None
              Biagio Manzari Biagio Manzari
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: