-
Notifications
You must be signed in to change notification settings - Fork 266
DNS zone error #1315
Comments
What version of Tectonic was this? Through a real release, or from master, etc? |
I'm seeing similar problem using
|
@robszumski @jasminSPC @s-urbaniak confirming that myself (and @tonytcampbell) are seeing this as well on Azure tectonic-installer runs:
This can be tracked to a vendor package: https://github.com/jen20/riviera/blob/master/azure/api.go#L5 I've opened a PR on that project to fix: jen20/riviera#24 |
what is the impact of this issue? |
@justaugustus great catch and thanks for submitting an upstream fix! |
@s-urbaniak I get this error message each time I try running the installer against Azure. @rajcheval There is a possible workaround if you were to checkout azure plugin and change this line to |
@jasminSPC gah, that seems to be region dependent then :-/ /cc @alexsomesan |
Ack @s-urbaniak. @rajcheval are you seeing the same problem when building across different Azure locations? |
@tombuildsstuff from HashiCorp is sheparding using the Azure SDK for Go for DNS interactions instead of jen20/riviera. |
@s-urbaniak I've tried using eastus, westcentralus, centralus and northeurope and each is returning the same error. |
Fix is pending release from Terraform, AFAICT at the moment. |
👋 Cross-posting this update here: I've just released version 0.1.4 of the AzureRM Provider which includes the fix for this, more details here: hashicorp/terraform-provider-azurerm#192 (comment) Thanks! |
@s-urbaniak @alexsomesan @jasminSPC or @metral -- |
Tested 0.1.4 of the AzureRM Provider in 3 different regions (northeurope, westeurope and centralus). |
I was not able to test this successfully. But it could be that TF didn't pull correct plugin. p.s. I'm using Terraform 0.10. dev. |
I built the provider myself, from the 0.1.4 tag.
…On Thu 27. Jul 2017 at 21:19, Jasmin Gacic ***@***.***> wrote:
I was not able to test this successfully. But it could be that TF didn't
pull correct plugin.
p.s. I'm using Terraform 0.10. dev.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1315 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABC-m0erXJ69RRe7VIeoPGgLuDpQlSxZks5sSOKigaJpZM4OQzI3>
.
|
Rebuilding it myself and testing it. |
Location
|
hey @jasminSPC @alexsomesan would love to get to the bottom of this. Azure DNS team reporting they have not obsoleted any APIs recently, and I am also able to successfully provision DNS Zone and A Record in both West US and North Europe. Using the config file below - basically, a sample from terraform.io. Can you provide a minimal config file that would allow me to replicate the issues you're seeing: resource "azurerm_resource_group" "test" { resource "azurerm_dns_zone" "test" { resource "azurerm_dns_a_record" "test" { |
@echuvyrov When I run the example you provided everything works fine.
But when I run tectonic-installer from the code
I can see that the the api-version is different now. When running apply i get this warning which is confirming that the plugin is indeed picked up by Terraform.
I looked into the code and I see this reference to the api-version 2016-04-01 https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/vendor/github.com/Azure/azure-sdk-for-go/arm/dns/recordsets.go#L88 Here are terraform.tfvars I used
To replicate what I just had simply follow these instructions under section |
@jasminSPC I think you may be running this with an older revision of the installer. Latest Azure templates in master don't attempt to create a DNS zone anymore, but rather expect a DNS zone resource ID as input var. I think that is why I was able to get successful build with the fixed provider. |
@alexsomesan I'm using |
Yes, `master` is also where I'm running from.
…On Mon, Jul 31, 2017 at 6:21 PM, Jasmin Gacic ***@***.***> wrote:
@alexsomesan <https://github.com/alexsomesan> I'm using master branch is
that the one I should be using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1315 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABC-m07KhQVaw5G7naPvOpT2TpIc0qsrks5sTf8NgaJpZM4OQzI3>
.
|
So I tried |
@alexsomesan did this land in Tectonic 1.7.1-tectonic.1? |
@robszumski The fix is done in the stand-alone Azure provider that was created with TF 0.10.0 and it's migration to stand-alone providers. AFIK it's not backported into 0.9.x. The installer still ships with Terraform 0.9.6 so it wouldn't have picked up the fix either because 0.9.6 is very old. |
@alexsomesan 👋 I'm not sure if you've seen my comment on this issue - but would it be possible to confirm if the resource group name is actually a name, rather than an ID? I've also opened an issue on the Terraform AzureRM Provider to add validation to catch this in future Thanks! |
@alexsomesan : any workarounds to get tectonic with your new Azure provider? Looking forward to the fix. Thanks. |
Still looks like a complete showstopper for Tectonic/Azure, with a release as recent as 1.7.1-tectonic.2
|
@jsilberm Sorry you're having issues! Have you had a chance to review our updated documentation for using Tectonic on Azure: https://coreos.com/tectonic/docs/latest/install/azure/azure-terraform.html Specifically, around DNS:
I believe you'll need to set
After a little testing, I found that when
Please let us know if that fixes it for you. /cc: @alexsomesan, @robszumski |
Indeed. Thanks for the help @justaugustus ! Feel free to close this issue. Much appreciated! |
Awesome, glad you got it worked out. |
hello,
was trying install tectonics through az console.
Error applying plan:
2 error(s) occurred:
module.dns.azurerm_dns_zone.tectonic_azure_dns_zone: 1 error(s) occurred:
azurerm_dns_zone.tectonic_azure_dns_zone: Error creating DNS Zone: InvalidApiVersionParameter (400) - The api-version '2015-05-04-preview' is invalid. The supported versions are '2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2
016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
module.resource_group.azurerm_resource_group.tectonic_cluster: azurerm_resource_group.tectonic_cluster: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue.
Please include the following information in your report:
ernetes", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Sensitive:false, Type:0x0}, "tags.%":*terraform.ResourceAttrDiff{Old:"0", New:"", NewComputed:true, NewRemoved:false, NewExtra:interface {}(nil
), RequiresNew:false, Sensitive:false, Type:0x0}, "location":*terraform.ResourceAttrDiff{Old:"northeurope", New:"", NewComputed:false, NewRemoved:false, NewExtra:"", RequiresNew:true, Sensitive:false, Type:0x0}}, Destroy:false, DestroyDe
posed:false, DestroyTainted:false, Meta:map[string]interface {}(nil)}
Diff Two (usually from apply): *terraform.InstanceDiff{mu:sync.Mutex{state:0, sema:0x0}, Attributes:map[string]*terraform.ResourceAttrDiff{"name":*terraform.ResourceAttrDiff{Old:"", New:"tectonic-cluster-kubernetes", NewComputed:fals
e, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, "tags.%":*terraform.ResourceAttrDiff{Old:"", New:"", NewComputed:true, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Sensit
ive:false, Type:0x0}}, Destroy:false, DestroyDeposed:false, DestroyTainted:false, Meta:map[string]interface {}(nil)}
Also include as much context as you can about your config, state, and the steps you performed to trigger this error.
I get this error while install, can anyone help me
The text was updated successfully, but these errors were encountered: