[Bug 2038109] Re: [SRU] Failed to create port on network <UUID>, because fixed_ips included invalid subnet <UUID>

[Andreas Hasenack]

I'm not understanding the [impact] and the [test plan].

In [impact], it says:
"""
When creating a new "cluster"that overrides the fixed network defined in the cluster template, but not the subnet.

It would be expected that the cluster create request fails with a 400 error since the client is submitting an invalid request.
"""

So we should fail, but don't.


Then the test plan says the opposite basically, saying it's expected the cluster be created, but we get an error instead:
"""
Expected result

The cluster gets created

Actual result:

The cluster creation fails with the following error:
"""

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/2038109

Title:
  [SRU] Failed to create port on network <UUID>, because fixed_ips
  included invalid subnet <UUID>

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive antelope series:
  In Progress
Status in Ubuntu Cloud Archive bobcat series:
  Won't Fix
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive yoga series:
  New
Status in Ubuntu Cloud Archive zed series:
  Won't Fix
Status in Magnum:
  Fix Released
Status in magnum package in Ubuntu:
  Fix Released
Status in magnum source package in Focal:
  In Progress
Status in magnum source package in Jammy:
  In Progress

Bug description:
  [Impact]

  When creating a new "cluster"that overrides the fixed network defined
  in the cluster template, but not the subnet.

  It would be expected that the cluster create request fails with a 400
  error since the client is submitting an invalid request.

  [Environment]

  Focal Ussuri

  [Test Case]

  1. Create a new cluster template WITHOUT a fixed network/subnet set.
  openstack coe cluster template create k8s-cluster-template \
      --image fedora-coreos-32 \
      --keypair testkey \
      --external-network ext_net \
      --flavor m1.small \
      --network-driver flannel \
      --coe kubernetes \
      --fixed-network admin_net \
      --fixed-subnet admin_subnet

  2. Create a new cluster using the template previously created and
  select an existing network

  openstack coe cluster create \
      --cluster-template k8s-cluster-template \
      --timeout 120 \
      --fixed-network private \
      k8scluster

  Expected result

  The cluster gets created

  Actual result:

  The cluster creation fails with the following error:

  $ openstack coe cluster show k8scluster -f json -c faults | jq -r '.faults'
  {
    "default-master": "Resource CREATE failed: BadRequest: resources.kube_masters.resources[0].resources.kube_master_eth0: Invalid input for operation: Failed to create port on network 525df7a4-1aeb-4eae-a37f-432a809a8161, because fixed_ips included invalid subnet 30e1b4ed-811f-4226-a19d-0a56cc72fc10.\nNeutron server returns request_ids: ['req-7a55a40a-3aa3-4a67-8ecf-b2e47ae16a84']",
    "default-worker": "Resource CREATE failed: BadRequest: resources.kube_masters.resources[0].resources.kube_master_eth0: Invalid input for operation: Failed to create port on network 525df7a4-1aeb-4eae-a37f-432a809a8161, because fixed_ips included invalid subnet 30e1b4ed-811f-4226-a19d-0a56cc72fc10.\nNeutron server returns request_ids: ['req-7a55a40a-3aa3-4a67-8ecf-b2e47ae16a84']"
  }

  [ Where problems could occur ]

  - This change introduces validation of the configuration passed by the
  user during the creation of a new cluster, issues can be raised during
  the creation of new clusters, but not for already created clusters.

  [ Other Info ]

  - The patches associated to this SRU were merged during the OpenStack 2024.1 (Caracal) devel cycle
  - Patches
    + https://opendev.org/openstack/magnum/commit/753baadbb8b5b4c3032d4618166b1c899a50fb07
    + https://opendev.org/openstack/magnum/commit/a8bce0bfee81218cd1c0ddcf3e2b86b96659933e

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions