Dangling security association record in DB after network delete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Vadym Markov |
Bug Description
Affected version:
Reproduced on Devstack/Yoga, but any recent environment with Manila should be affected
Steps to reproduce:
1. Create security service:
manila security-
2. Create share network:
manila share-network-
3. Associate them:
manila share-network-
4. Delete network:
manila share-network-
After it, we have a non-deleted record in share_network_
tags: | added: db |
Changed in manila: | |
assignee: | nobody → Vadym Markov (vmarkov) |
Changed in manila: | |
milestone: | none → bobcat-3 |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in manila: | |
milestone: | bobcat-3 → bobcat-rc1 |
Changed in manila: | |
milestone: | bobcat-rc1 → caracal-1 |
See additional related discussions at https:/ /meetings. opendev. org/meetings/ manila/ 2023/manila. 2023-08- 03-15.00. log.html