Activity log for bug #2038109

Date Who What changed Old value New value Message
2023-10-02 16:10:04 Felipe Reyes bug added bug
2023-10-02 16:10:27 Felipe Reyes magnum (Ubuntu): status New Confirmed
2023-10-03 19:57:57 Felipe Reyes bug task added magnum
2023-10-04 14:28:40 Felipe Reyes magnum: assignee Felipe Reyes (freyes)
2023-10-04 14:28:47 Felipe Reyes magnum: status New In Progress
2024-01-10 12:35:27 OpenStack Infra magnum: status In Progress Fix Released
2024-07-17 19:47:05 Felipe Reyes nominated for series Ubuntu Focal
2024-07-17 19:47:05 Felipe Reyes bug task added magnum (Ubuntu Focal)
2024-07-17 19:47:05 Felipe Reyes nominated for series Ubuntu Jammy
2024-07-17 19:47:05 Felipe Reyes bug task added magnum (Ubuntu Jammy)
2024-07-17 19:47:23 Felipe Reyes bug task added cloud-archive
2024-07-17 19:50:31 Felipe Reyes nominated for series cloud-archive/yoga
2024-07-17 19:50:31 Felipe Reyes bug task added cloud-archive/yoga
2024-07-17 19:50:31 Felipe Reyes nominated for series cloud-archive/zed
2024-07-17 19:50:31 Felipe Reyes bug task added cloud-archive/zed
2024-07-17 19:50:31 Felipe Reyes nominated for series cloud-archive/bobcat
2024-07-17 19:50:31 Felipe Reyes bug task added cloud-archive/bobcat
2024-07-17 19:50:31 Felipe Reyes nominated for series cloud-archive/antelope
2024-07-17 19:50:31 Felipe Reyes bug task added cloud-archive/antelope
2024-07-17 19:50:31 Felipe Reyes nominated for series cloud-archive/ussuri
2024-07-17 19:50:31 Felipe Reyes bug task added cloud-archive/ussuri
2024-07-17 19:53:38 Felipe Reyes cloud-archive: status New Invalid
2024-07-17 19:54:40 Felipe Reyes attachment added lp2038109_antelope.debdiff https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798098/+files/lp2038109_antelope.debdiff
2024-07-17 19:57:10 Felipe Reyes attachment added lp2038109_bobcat.debdiff https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798099/+files/lp2038109_bobcat.debdiff
2024-07-17 19:58:52 Felipe Reyes attachment added lp2038109_zed.debdiff https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798100/+files/lp2038109_zed.debdiff
2024-07-17 19:59:12 Felipe Reyes cloud-archive/antelope: status New In Progress
2024-07-17 19:59:27 Felipe Reyes cloud-archive/bobcat: status New In Progress
2024-07-17 19:59:41 Felipe Reyes cloud-archive/zed: status New In Progress
2024-07-17 20:01:03 Felipe Reyes attachment added lp2038109_jammy.debdiff https://bugs.launchpad.net/cloud-archive/zed/+bug/2038109/+attachment/5798101/+files/lp2038109_jammy.debdiff
2024-07-17 20:01:26 Felipe Reyes magnum (Ubuntu Jammy): status New In Progress
2024-07-17 20:04:39 Felipe Reyes attachment added lp2038109_focal.debdiff https://bugs.launchpad.net/ubuntu/jammy/+source/magnum/+bug/2038109/+attachment/5798102/+files/lp2038109_focal.debdiff
2024-07-17 20:05:08 Felipe Reyes magnum (Ubuntu Focal): status New In Progress
2024-07-17 20:31:19 Ubuntu Foundations Team Bug Bot tags patch
2024-07-17 20:31:28 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors
2024-08-01 15:45:52 Felipe Reyes cloud-archive/zed: status In Progress Won't Fix
2024-08-01 16:03:08 Felipe Reyes attachment removed lp2038109_zed.debdiff https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/2038109/+attachment/5798100/+files/lp2038109_zed.debdiff
2024-08-01 16:04:12 Felipe Reyes cloud-archive/bobcat: status In Progress Won't Fix
2024-08-01 16:05:22 Felipe Reyes summary Failed to create port on network <UUID>, because fixed_ips included invalid subnet <UUID> [SRU] Failed to create port on network <UUID>, because fixed_ips included invalid subnet <UUID>
2024-08-01 16:22:20 Felipe Reyes 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']" } [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
2024-08-02 21:46:40 Launchpad Janitor merge proposal linked https://code.launchpad.net/~freyes/ubuntu/+source/magnum/+git/magnum/+merge/470598