Cannot set some attributes to default values after setting
Bug #1086232 reported by
yong sheng gong
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
yong sheng gong | ||
python-neutronclient |
Fix Released
|
Medium
|
yong sheng gong |
Bug Description
Helo,
We cannot set some attributes into default or none after setting it.
For example,
we can run quantum subnet-create net1 10.0.1.0/24 --dns_nameservers server1 server2
but we will not be able to clear it.
This bug is related to our validation logics and CLI command.
on server side: our validation logic is demanding some thing to validate, they don't think None is validate value.
On client command side, we is not able to specify the None value for an attribute.
Changed in python-quantumclient: | |
importance: | Undecided → Medium |
Changed in quantum: | |
importance: | Undecided → Medium |
milestone: | none → grizzly-2 |
Changed in python-quantumclient: | |
assignee: | nobody → yong sheng gong (gongysh) |
Changed in quantum: | |
assignee: | nobody → yong sheng gong (gongysh) |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-2 → 2013.1 |
Changed in python-neutronclient: | |
milestone: | none → 2.2.1-2.2.6 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/17436
Review: https:/