2.4.0 broke existing subnet create calls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Fix Released
|
High
|
Zengfa Gao |
Bug Description
It appears that the 2.4.0 release broke subnet create calls.
Looking at this review [1], you can see a subnet create call like this:
neutron --os-tenant-name accounts-test-$i --os-password pass --os-username accounts-test--$i \
subnet-create network-$i --name subnet-$i --gateway 10.0.$i.1 10.0.$i.0/24
Looking at the logs for this [2], you can see a failure (copied below):
2015-04-10 17:34:50.665 | ++ neutron --os-tenant-name accounts-test-1 --os-password pass --os-username accounts-test--1 subnet-create network-1 --name subnet-1 --gateway 10.0.1.1 10.0.1.0/24
2015-04-10 17:34:51.467 | Invalid values_specs 10.0.1.0/24
[1] https:/
[2] http://
Changed in python-neutronclient: | |
milestone: | 2.4.1 → none |
milestone: | none → 2.6.0 |
status: | Fix Committed → Fix Released |
We're thinking this review may be the culprit:
https:/ /review. openstack. org/#/c/ 165910/ 6