-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_key_vault
: waiting for 10 successful dns locators before returning as created
#1081
Conversation
azurerm_key_vault
: waiting for 10 successful dns locators before returning as createdazurerm_key_vault
: waiting for 10 successful dns locators before returning as created
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 assuming relevant tests pass
dac5117
to
847c521
Compare
@tombuildsstuff was this merged to 1.3.3? Doesn't seem like it.. |
@pixelicous not yet, this is still WIP as this fix needs some additional tweaking |
@tombuildsstuff thx! We opened a ficket with MS about this, as its related.. I remember writing you an official response from MS about how to handle that timeout but i cant seem to find which post it was on.. Ill post it again here if i dont find it soon, they are implementing a few changes but ita going to take a while probably |
87c7036
to
676aeab
Compare
676aeab
to
4d785b9
Compare
azurerm_key_vault
: waiting for 10 successful dns locators before returning as createdazurerm_key_vault
: waiting for 10 successful dns locators before returning as created
Also now fixes #1005 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
hey @pixelicous Just to let you know that v1.4.0 of the Azure Provider has been released which includes the fix for this :) Thanks! |
@tombuildsstuff hey! i saw :) amazing, and just as i decided to implement the null_resource with a sleep 😄 kudos for the quick timeframe between 1.3.3 and 1.4 🔥 ❕ |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Switching over to ensure the DNS is resolved 10 times in a row before marking the KeyVault resource as successfully provisioned.
This should fix #655 but it's hard to tell since it fails sporadically: