Checking the list of reverse dependencies of python3-magnumclient in focal:
$ apt-cache rdepends python3-magnumclient
python3-magnumclient
Reverse Depends:
python3-mistral
python3-mistral
python3-heat
python3-heat
python3-magnum-ui
Assuming these are all openstack components and are not used outside of
openstack, does the [test case] cover these components as well?
Specifically mistral and heat?
Is there any sort of release notes available for 3.0.1, or any of the
others that are compatible with what is in focal? And why did you pick
3.0.1, and not, say, 2.17.0 for example? Did you analyze the diff and
conclude there are no backwards incompatible changes being introduced?
** Changed in: python-magnumclient (Ubuntu Focal)
Status: Triaged => Incomplete
--
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/1996229
Title:
[SRU] magnum ui can not delete the coe cluster
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive ussuri series:
Won't Fix
Status in magnum-ui package in Ubuntu:
Invalid
Status in python-magnumclient package in Ubuntu:
Invalid
Status in python-magnumclient source package in Focal:
Incomplete
Bug description:
[ Impact ]
When trying to manipulate objects over the Magnum API (container-infra endpoint)
the client available in the Ubuntu 20.04 archive implements an older and
incompatible API version (1.1 instead of 1.9), this makes impossible to complete
certain operations like creating and destroy clusters.
For example when creating clusters the following error is returned by
Horizon:
"Key must be in
name,node_count,discovery_url,master_count,baymodel_id,bay_create_timeout,cluster_template_id,create_timeout,keypair,docker_volume_size,labels,master_flavor_id,flavor_id"
This is because manugm-ui is passing keys that magnumclient is not
aware of.
The list of python-magnumclient releases for the Ussuri (Focal)
release is available at [0], the versions compatible are 2.17.0, 3.0.0
and 3.0.1, while the version shipped in Ubuntu 20.04 is 2.11.0 which
corresponds to the version released during the OpenStack Stein
cycle[1]
[0] https://releases.openstack.org/teams/magnum.html#team-ussuri-python-magnumclient
[1] https://releases.openstack.org/teams/magnum.html#team-stein-python-magnumclient
[ Test Plan ]
Steps to reproduce:
1. Deploy a Magnum based environment with charmed-openstack-tester
git clone https://github.com/openstack-charmers/charmed-openstack-tester.git
cd charmed-openstack-tester
tox -e func-target -- keystone_v3_smoke_focal_magnum:focal-ussuri-magnum
2. Once the deployment has completed go Horizon and follow these
steps:
- Create Cluster Template object with any configuration and name it "k8s-template"
- Create a Cluster based on the previosly created template ("k8s-template")
Expected result:
- A new cluster is spawn
Actual result:
- The cluster fails to be created, Horizon displays a notification without details of the failure
- Looking into Firefox developer tools network the followin error can be found in a 400 error request to Horizon:
"Key must be in
name,node_count,discovery_url,master_count,baymodel_id,bay_create_timeout,cluster_template_id,create_timeout,keypair,docker_volume_size,labels,master_flavor_id,flavor_id"
[ Where problems could occur ]
* The main component in an OpenStack cloud that consumes python-
magnumclient is Horizon when the magnum-ui package is installed and
enabled, any issues with this SRU would express with the inability to
manipulate Magnum containers from the web UI, errors would show up in
/var/log/apache2/error.log where any stacktrace would be logged.
* Other consumer of this package is actual final users trying to
manage their Magnum containers from the CLI, problems with this
package would have the symptom of incompatible APIs versions, although
the client is capable of downgrading to a API version compatible.
[ Other Info ]
* This SRU brings onboard 52 new commits
$ git log --oneline 2.11.0..3.0.1 | wc -l
52
* There are 7 releases between 2.11.0 and 3.0.1, which it's a lot for
a SRU, although since the version shipped in Focal is not correctly
aligned with the version upstream released for Ussuri (the version
shipped in Focal), users will be better served with a one time bump up
of the package.
[Original description]
Try to delete the coe cluster through magnum UI. It removes the entry
from UI immediately, but when we refresh the dashboard interface
cluster, it appears again. It happens on packages magnum-ui from
Ussuri on Focal. Did not try with latest version of Openstack.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1996229/+subscriptions