Deleting managed recordsets should provide meaningful exception message.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Low
|
Alex Barclay |
Bug Description
vyom@vyom:~$ openstack zone list
+------
| id | name | type | serial | status | action |
+------
| 78dd3e3d-
| fdc7012f-
+------
vyom@vyom:~$ openstack recordset list 78dd3e3d-
+------
| id | name | type | records |
+------
| d8de08e0-
| f1ef04b3-
+------
While we try to delete NS records we get exception message as follows :
vyom@vyom:~$ openstack recordset delete 78dd3e3d-
Managed records may not be updated
This message should be something like
"Managed records can not be deleted"
or
"Deleting a NS recordset is not allowed"
Changed in python-designateclient: | |
assignee: | nobody → megha (tmegha247) |
affects: | python-designateclient → designate |
Changed in designate: | |
status: | New → Triaged |
summary: |
- 'openstack recordset delete ' command should provide meaningful - exception message. + Deleting managed recordsets should provide meaningful exception message. |
Changed in designate: | |
importance: | Undecided → Low |
status: | Triaged → Confirmed |
Changed in designate: | |
assignee: | megha (tmegha247) → Alex Barclay (9lex) |
milestone: | none → mitaka-2 |
status: | Confirmed → Triaged |
Changed in designate: | |
status: | Triaged → In Progress |
This error message comes from within Designate, and a case should be added for Deleting to get a better message to clients/users.