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

Creating a NetworkAttachmentDefinition from the console always ends up in the Default namespace with the wrong name

XMLWordPrintable

    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      NetworkAttachmentDefinition always gets created in the default namespace if I use the form method "from the console".
      It also doesn't honor the selected name and creates the NAD object with a different name (the selected name + random suffix).

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

      OCP 4.15.5

      How reproducible:

      From the console, under the Networking section, select NetworkAttachmentDefinitions and create a NAD using the Form method and not the YAML one.

      Actual results:

      The NAD gets created in the wrong namespace (always ends up in the default namespace) and with the wrong name.

      Expected results:

      The NAD resource gets created in the currently selected namespace with the chosen name

            phbailey@redhat.com Phillip Rhodes
            rhn-support-aelganzo Amr Elganzory
            Yanping Zhang Yanping Zhang
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: