Make set/unset commands end up normally when nothing specified
Bug #1588588 reported by
Tang Chen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Medium
|
aohuanxuan |
Bug Description
In the IRC meeting on 20160602, we have agreed on that set/unset commands should ends up normally instead of raising an exception when nothing is specified to modify. The main reason is: When nothing is specified, the command sets/unsets nothing, which is a normal behavior, and ends up normally. No API call fails. No error happens.
So, just fix all set/unset commands who are raising exception.
Changed in python-openstackclient: | |
assignee: | nobody → Tang Chen (tangchen) |
Changed in python-openstackclient: | |
status: | In Progress → Fix Committed |
Changed in python-openstackclient: | |
importance: | Undecided → Medium |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/325063
Review: https:/