Repository navigation
Passing invalid "Openstack-Api-Version: container-infrastructure-management: " to magnum #3429
Description
When specifying API version to Openstack Magnum, gophercloud is passing an invalid string which results in a 406.
I don't understand how the aliasing is meant to work, but I believe that the problem was introduced here:
e394733#diff-5643779347824e0ec4258ef187be1f23c3b1eeca504fcfe48e47efe0e051b4bfL480
I don't see the string 'container-infrastructure-management' anywhere in Magnum source code; the version string should be 'container-infra' which was the value before that patch. Here's an example of the magnum client passing that string to switch API version:
The naive fix is probably just to switch that string back to 'container-infra' which is what the API expects. I'm happy to write that patch but want to make sure there's not a more complicated bug in the aliasing code first.
For reference, our internal tracking of this issue is https://phabricator.wikimedia.org/T397106
Activity
github-actions commentedon Jun 17, 2025
Thank you for reporting your first issue! Be sure that we will be looking at it, but keep in mind
this sometimes takes a while.
Please let the maintainers know if your issue has not got enough attention after a few days.
If any doubt, please consult our issue tutorial.
Use official service types
stephenfin commentedon Jun 18, 2025
This is a bug in Magnum, which is should be respecting the official service type. I have pushed a fix here. However, we're going to need to support older deployments without this fix so yes, we'll need to insist on using
container-infrafor theOpenStack-API-Versionheader. I'll work on the fix.Use container-infra for OpenStack-API-Version
Use container-infra for OpenStack-API-Version