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

[Felipe Reyes]

The jammy-antelope validation was successful, the UI provides an option
to set a subnet as shown in the attached images (before and after the
upgrade to proposed), here it's the terminal log of the versions and
upgrade process

$ juju ssh openstack-dashboard/leader sudo -i
root at juju-9e541a-jammy-antelope-18:~# apt policy python3-magnum-ui
python3-magnum-ui:
  Installed: 12.0.0-0ubuntu1~cloud0
  Candidate: 12.0.0-0ubuntu1~cloud0
  Version table:
 *** 12.0.0-0ubuntu1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope/main amd64 Packages
        100 /var/lib/dpkg/status
     10.0.0-0ubuntu3 500
        500 http://availability-zone-2.clouds.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
root at juju-9e541a-jammy-antelope-18:~# vim /etc/apt/sources.list
root at juju-9e541a-jammy-antelope-18:~# apt-get update -qq
root at juju-9e541a-jammy-antelope-18:~# apt policy python3-magnum-ui
python3-magnum-ui:
  Installed: 12.0.0-0ubuntu1~cloud0
  Candidate: 12.0.0-0ubuntu1~cloud0
  Version table:
 *** 12.0.0-0ubuntu1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope/main amd64 Packages
        100 /var/lib/dpkg/status
     10.0.0-0ubuntu3.1 500
        500 http://availability-zone-2.clouds.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages
     10.0.0-0ubuntu3 500
        500 http://availability-zone-2.clouds.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
root at juju-9e541a-jammy-antelope-18:~# apt install --only-upgrade python3-magnum-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-magnum-ui is already the newest version (12.0.0-0ubuntu1~cloud0).
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
root at juju-9e541a-jammy-antelope-18:~# vim /etc/apt/sources.list.d/cloud-archive.list
root at juju-9e541a-jammy-antelope-18:~# apt-get update -qq
root at juju-9e541a-jammy-antelope-18:~# apt policy python3-magnum-ui
python3-magnum-ui:
  Installed: 12.0.0-0ubuntu1~cloud0
  Candidate: 12.0.0-0ubuntu1.1~cloud0
  Version table:
     12.0.0-0ubuntu1.1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-proposed/antelope/main amd64 Packages
 *** 12.0.0-0ubuntu1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope/main amd64 Packages
        100 /var/lib/dpkg/status
     10.0.0-0ubuntu3.1 500
        500 http://availability-zone-2.clouds.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages
     10.0.0-0ubuntu3 500
        500 http://availability-zone-2.clouds.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
root at juju-9e541a-jammy-antelope-18:~# apt install --only-upgrade python3-magnum-ui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  python3-magnum-ui
1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Need to get 79.5 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-proposed/antelope/main amd64 python3-magnum-ui all 12.0.0-0ubuntu1.1~cloud0 [79.5 kB]
Fetched 79.5 kB in 0s (721 kB/s)
(Reading database ... 119982 files and directories currently installed.)
Preparing to unpack .../python3-magnum-ui_12.0.0-0ubuntu1.1~cloud0_all.deb ...
Unpacking python3-magnum-ui (12.0.0-0ubuntu1.1~cloud0) over (12.0.0-0ubuntu1~cloud0) ...
Setting up python3-magnum-ui (12.0.0-0ubuntu1.1~cloud0) ...
Scanning processes...
Scanning candidates...
Scanning linux images...

Restarting services...
 systemctl restart packagekit.service polkit.service
Service restarts being deferred:
 systemctl restart networkd-dispatcher.service
 systemctl restart unattended-upgrades.service

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
root at juju-9e541a-jammy-antelope-18:~#
root at juju-9e541a-jammy-antelope-18:~# systemctl restart apache2
root at juju-9e541a-jammy-antelope-18:~#

-- 
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:
  [SRU] 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:
  Fix Committed
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:
  Fix Committed
Status in magnum-ui source package in Jammy:
  Fix Committed

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. Deploy an OpenStack cloud with the magnum-ui extension installed.
  ```
  git clone https://opendev.org/openstack/charm-magnum-dashboard
  cd charm-magnum-dashboard
  git checkout stable/${VERSION}  # ${VERSION} can be 2023.1, yoga or ussuri.
  tox -e build
  tox -e func-target -- ${BUNDLE}  # ${BUNDLE} can be jammy-antelope, jammy-yoga or focal-ussuri
  ```

  2. Create a new cluster template with a fixed_network test-net and fixed_subnet test-subnet
  3. 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.

  [ Where problems could occur ]

  This is a javascript (Angular) code change, issues can be detected
  using the Web Developer Tools console where a javascript exeception
  may be raised.

  Another source of problems is that this code change adds a handler
  when populate the list of subnets when the network is changed in the
  "Fixed Network" dropdown list, if there were issues the subnet list
  would be rendered empty.

  [ Other Info ]

  - This bug fix was merged during the 2024.1 (Caracal) development cycle - https://review.opendev.org/c/openstack/magnum-ui/+/898007
  - The commit that fixes this issue is available since magnum-ui-14.0.0 - https://opendev.org/openstack/magnum-ui/commit/6f6c3db282fe2f0e08ad69c557eb153858b0164a
  - This bug fix is not relevant for upgrades, it's purely UI fix
  - This change is adding a new UI component, which on the surface may look like not suitable for a SRU, although the current UI induces users to get into a broken configuration for new clusters when overriding the cluster template's network.

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