When used in 'manila access-allow' 172.17.5.13 and 172.17.5.13/32 select the same single IP; as do 2620:52:0:13b8::fe:e7 and 2620:52:0:13b8::fe:e7/128. Yet one can do 'manila access-allow' for all of these with contradictory access_level specifications so that it is ambiguous whether access should be read-write or read-only for a given host.
(overcloud) [stack@undercloud-0 ~]$ manila access-list bcf04572-de15-42d6-b325-9a269bd643a9
+--------------------------------------+-------------+---------------------------+--------------+--------+------------+----------------------------+------------+
| id | access_type | access_to | access_level | state | access_key | created_at | updated_at |
+--------------------------------------+-------------+---------------------------+--------------+--------+------------+----------------------------+------------+
| 11131651-705d-4e11-8e3f-0dcd9c6e1a6e | ip | 172.17.5.13 | rw | active | None | 2018-04-26T19:09:06.000000 | None |
| 355e6ee3-a5cd-47ee-9352-a806f27ba00d | ip | 2620:52:0:13b8::fe:e7 | rw | active | None | 2018-04-27T15:22:48.000000 | None |
| 43420eb0-513e-4a2d-bda1-843484a50bf3 | ip | 172.17.5.13/32 | ro | active | None | 2018-04-27T16:05:32.000000 | None |
| 9edeb9c3-f5fb-4b8f-9a39-8c96f60cd79b | ip | 2620:52:0:13b8::fe:e7/128 | ro | active | None | 2018-04-27T16:06:04.000000 | None |
+--------------------------------------+-------------+---------------------------+--------------+--------+------------+----------------------------+------------+
The API should generate a CONFLICT error when contradictory access-allow commands are entered, just as it does when one issues and access allow command for a host address or for a prefix for which there is already an access rule.
The fix for this bug should include API tests to detect regressions