A few questions for you:
What release version of OpenStack Manila are you running? What distribution?
At the outset, the driver shouldn't be erring on this path when attempting to delete a non-existing rule. But I'm confused as to why this rule was non-existing. We haven't seen this issue in our testing, so it'd be useful if you have the complete manila-share log that you can provide so we can backtrack and see what happened with the rule for your client (172.16.180.5).
Hi,
A few questions for you:
What release version of OpenStack Manila are you running? What distribution?
At the outset, the driver shouldn't be erring on this path when attempting to delete a non-existing rule. But I'm confused as to why this rule was non-existing. We haven't seen this issue in our testing, so it'd be useful if you have the complete manila-share log that you can provide so we can backtrack and see what happened with the rule for your client (172.16.180.5).
Thanks!