Title
-----
rate_limit error when executing openstack network commands
This issue was reported by Shuicheng Lin
Brief Description
-----------------
When attempting to run openstack networking commands as part of system provisioning, an error is returned as follows:
controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID}
__init__() got an unexpected keyword argument 'rate_limit'
controller-0:/home/wrsroot# openstack network list
__init__() got an unexpected keyword argument 'rate_limit'
Severity
--------
Major: This impacts configuring networking on recent StarlingX loads; started on Mar 5.
Steps to Reproduce
------------------
run any openstack network command
Expected Behavior
------------------
Command should pass
Actual Behavior
----------------
Commands fail as per above
Reproducibility
---------------
100% reproducible
System Configuration
--------------------
Any
Branch/Pull Time/Commit
-----------------------
master as of March 5 afternoon
From Joseph Richard:
In https://github.com/openstack/openstacksdk/blame/da4ec3e70c20db3ea37cd54dec6dc1e10b309274/lower-constraints.txt, a dependency was added for keystoneauth1==3.13.0, however it looks like StarlingX is only at 3.10.0. Because we are building openstacksdk from master, we are hitting this. We will likely need to upversion keystoneauth1 to resolve this.
Timestamp/Logs
--------------
Not required; issue is reproducible
From Don Penney:
This should just be a matter of updating the RPM version being downloaded, as we aren’t rebuilding it:
stx-tools/
python2-
There should be a check of other RPM versions, as well, though, in case anything else needs to be updated.