Closed dougwig closed 8 years ago
Fixed in 1.4.1
“Issue reported with heat deleting a full LB; pool fails because hm still associated. We should auto-dis-associate, if not already.”
Auto-disassociate hm on pool delete (if not done already)
Upgrade to the latest version of a10-neutron-lbaas
1. Created a working heat stack with a lb, pool, and monitor using ACOS 4.0.3-GA
a10-neutron-lbaas on origin/master
2. Observed creation of resources on appliance
3. Deleted the working stack without errors
5. Observed deletion of resources on appliance
6. Created a working heat stack with a lb, pool, and monitor using ACOS 4.0.3-GA
a10-neutron-lbaas on tag/1.3.6
7. Observed creation of resources on appliance
8. Tried to delete the working stack and reproduced client errors
9. Switched to origin/master and deleted the stack from 1.3.6
10. Repeated steps 1-5 to confirm upgrading to master fixed the issue
... because hm still associated. We should auto-dis-associate, if not already.