Neutron SecGroup API should validate group name
Bug #1161411 reported by
Phil Day
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Unassigned |
Bug Description
The validation of names and groups comes from the security group API driver validate_property() method, and the NativeNovaSecur
Normally an empty name is not an issue, since all SG APIs are based on the ID of the group. However the action to add an instance to a security group takes a name not an ID - and will not accept an empty name. Hence for consistency with Nova behavior the QuantumSecurity
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → havana-1 |
Changed in nova: | |
milestone: | havana-1 → havana-2 |
Changed in nova: | |
milestone: | havana-2 → havana-3 |
Changed in nova: | |
milestone: | havana-3 → havana-rc1 |
Changed in nova: | |
milestone: | havana-rc1 → none |
status: | In Progress → Incomplete |
summary: |
- Quantum SecGroup API should validate group name + Neutron SecGroup API should validate group name |
Changed in nova: | |
assignee: | Ala Rezmerita (arezmerita) → nobody |
To post a comment you must log in.
I'm not sure this is needed if "API to add instance to a SecGroup should take ID not Name" (https:/ /bugs.launchpad .net/nova/ +bug/1161473) gets done.