Floating IP reservation via CLI fails with required_floatingips parameter

Bug #1843258 reported by Pierre Riteau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
New
High
Pierre Riteau

Bug Description

The blazar CLI passes the required_floatingips parameter to the API as a string instead of a list, resulting in the following error returned by the API:

$ blazar lease-create --reservation 'resource_type=virtual:floatingip,network_id=81fabec7-00ae-497a-b485-72f4bf187d3e,required_floatingips=["172.24.4.102"],amount=1' fip-lease
Matches: (u'resource_type=virtual:floatingip,network_id=81fabec7-00ae-497a-b485-72f4bf187d3e,required_floatingips=["172.24.4.102"]', u'amount', u'1')
Matches: (u'resource_type=virtual:floatingip,network_id=81fabec7-00ae-497a-b485-72f4bf187d3e', u'required_floatingips', u'["172.24.4.102"]')
Matches: (u'resource_type=virtual:floatingip', u'network_id', u'81fabec7-00ae-497a-b485-72f4bf187d3e')
Matches: (None, u'resource_type', u'virtual:floatingip')
ERROR: IP address [ is invalid form.

Revision history for this message
Tetsuro Nakamura (tetsuro0907) wrote :

Manual link:

Fix proposed in https://review.opendev.org/#/c/680989

Changed in blazar:
importance: Undecided → High
assignee: nobody → Pierre Riteau (priteau)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-blazarclient 2.2.1

This issue was fixed in the openstack/python-blazarclient 2.2.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.