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

Non-existant additional network ID makes CAPO panic

XMLWordPrintable

    • -
    • Low
    • No
    • ShiftStack Sprint 255, ShiftStack Sprint 256
    • 2
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      Description of problem:

      cluster-api-provider-openstack panics when fed a non-existant network ID as the additional network of a Machine. Or as any network where to create a port really.

This issue has been fixed upstream in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2064, which is present in the latest release v0.10.3.

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

      How reproducible:

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      Expected results:

      Additional info:

            pprinett@redhat.com Pierre Prinetti
            pprinett@redhat.com Pierre Prinetti
            Ramón Lobillo Ramón Lobillo
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: