`openstack network list --external` breaks with openstacksdk 0.11.0 + openstackclient 3.14.0
Bug #1746535 reported by
Luigi Toscano
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack SDK |
Fix Released
|
Undecided
|
Adrian Turjak |
Bug Description
tl;dr:
$ openstack network list --external
Invalid query params: router:external
The above command works with openstackclient 3.14.0+openstacksdk 0.9.19.
It is correct that upper-constrain
From a quick IRC discussion with morderd, openstackclient 3.14.0 should work with openstacksdk 0.11.0, so this bug is assigned directly to openstacksdk.
To post a comment you must log in.
This was introduced by https:/ /review. openstack. org/#/c/ 532723/ as this made the query params checking be strict about what was supplied so consumers weren't attempting to do bogus queries and expecting results. This causes us to fail loudly.
Problem here is that the openstackclient is actually supplying both the server-side name, and the client-side name: https:/ /github. com/openstack/ python- openstackclient /blob/master/ openstackclient /network/ v2/network. py#L500- L501
This worked because previously the server-side name was just dropped on the floor and silently ignored, but the client-side name was used, hence why the queries returned correctly.
Fix is to allow both server-side and client-side names as query pararms, but take precedence when both are supplied for the client-side ones. This gives us the strictness we want, while fixing this case where a consumer used both, or server-side names.