[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster

[Felipe Reyes]

Zed is EOL

** Changed in: cloud-archive/zed
       Status: New => Won't Fix

-- 
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/2038663

Title:
  no option to override the fixed_subnet when creating a new cluster

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive antelope series:
  New
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 UI:
  Fix Released
Status in magnum-ui package in Ubuntu:
  Invalid
Status in magnum-ui source package in Focal:
  New
Status in magnum-ui source package in Jammy:
  New

Bug description:
  [Impact]

  When a cluster template sets fixed_network and fixed_subnet and the
  user tries to create a new cluster using that template and decides to
  override the network, the fixed_subnet will inherited from the
  template, leaving an invalid configuration and later Neutron will
  refuse to allocate a port (since the subnet doesn't belong to the
  network). For more details see
  https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/2038109

  [Test Case]

  1. Create a new cluster template with a fixed_network test-net and fixed_subnet test-subnet
  2. Create a new cluster, uncheck the option "Create new network" and pick a network different from test-net in the dropdown list.

  Expected result:

  The cluster gets created

  Actual result:

  The cluster creation fails, because the network configuration is
  invalid.

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