Delete zone action needs manual config reload when using Infoblox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Undecided
|
Scott Solkhon |
Bug Description
When using Infoblox as a backend for Designate a zone will go into an ERROR state when it is deleted. To work around this you need to log into the Infoblox appliance and reload the running configuration by pressing the "restart configuration" button, and then issue another `openstack zone delete` command once this is complete.
This is not the same when you create a zone. Some investigation into the code found that the create_zone_auth() function in "designate/
If we compare this to the delete_zone_auth() function we see that it does not pass in the parameter restart_if_needed. This causes the zone to be deleted in Infoblox but the appliance will not reload without manual intervention from an admin. Without this manual intervention the polling action will time out and the zone will go into ERROR state.
Some digging into the Infoblox API documentation shows that 'restart_if_needed' is not supported on a delete zone call, and this suggests why it is not in place already for the provider. However, I have found that there is an API call to restart the Infoblox DNS services though the API, and you can pass this with a parameter to only do this if Infoblox is in a pending restart state for extra caution. i.e:
curl -k1 -u admin:Infoblox -H "Content-
Would it be possible to implement this kind of logic into the provider to fix this bug?
Fix proposed to branch: master /review. opendev. org/744013
Review: https:/