Subnet set removes existing values for repeated options
Bug #1564447 reported by
Richard Theis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As indicated by http://
Note: Unset support for these options is tracked under the following blueprint: https:/
description: | updated |
Changed in python-openstackclient: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in python-openstackclient: | |
assignee: | nobody → Reedip (reedip-banerjee) |
Changed in python-openstackclient: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Hey Richard,
I have a query
Consider for example, that user has set allocation_pools as 1.1.1.2/24 to 1.1.1.254/24 for his subnet.
Now he wants to change this.
Earlier, he could simply Update( in Neutronclient) or Set ( in OSC) to correct this
Now, in order to fix this, he has to run 2 commands ,
a) Unset
b) Set
I think that this use case should also be handled that allows user to Overwrite the existing information than append!
What do you think?