Repository navigation
ci(magnum): deprecate heat and use magnum-cluster-api driver - #3765
Conversation
github-actions
Bot
added
edit:actions
|
coverage: 63.54%. remained the same — winiciusallan:change-magnum-ci into gophercloud:main |
|
The error on master branch has an upstream bug report on Launchpad. It looks like a consequence of migrating to use the openstacksdk. |
As a follow-up, I've proposed a patch for this issue. Let's see if we can get it merged. |
|
The error on Epoxy is because this release has been using the I filed an issue in vexxhost/magnum-cluster-api vexxhost/magnum-cluster-api#1045 |
|
Hey @stephenfin, do you have any suggestions for how to workaround the issue above? Looking at the history, we added the build-isolation flag to work around the I saw Gnocchi adding a validation to skip this. I'm not sure about the likelihood of doing this upstream for the vexxhost repository. |
510e8cb to
f837dad
Compare
9bc85fb to
dc7b43b
Compare
|
Failed to backport PR to |
3 participants
As Magnum moved towards removing the Heat driver to use out-of-tree drivers instead[1], we cannot rely on it anymore in our CI. This pull request changes the
functional-containerinfrajob to use thevexxhost/magnum-cluster-api[2] plugin that's also being used upstream[3].The Vexxhost's driver spins up a Kubernetes cluster using Kind, installs all the dependencies, such as: kubectl, clusterctl, and CAPI, with OpenStack as the infrastructure provider (so we also have ORC here 🤩 ).
Let's see how it goes.
[1] https://review.opendev.org/c/openstack/magnum/+/985348
[2] https://github.com/vexxhost/magnum-cluster-api
[3] https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/987846