Comment 6 for bug 1550258

This behavior with access rules was fixed in the ocata release of openstack [1]. The changes were not back ported to newton or prior releases since it changes the API and the database schema in significant backwards-incompatible ways.

Sadly, the user experience with access rules prior to [1] was that if any incorrect rules are added, the whole rule set will be set to "error" state, and the only way to recover is to remove the incorrect rule. If a bulk operation was made or if access rules were added in quick succession, it's hard to pin point which specific rule caused the access rules to all be set to "error". This was acknowledged as bad user experience. Please upgrade and use newer versions of manila.

[1] https://review.openstack.org/#/c/369668/