-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
time parameter #16950
Comments
Hi @LaneEnglot, Sorry, I'm not sure what the question is here exactly. I expect this might be an azurerm provider related issue, but do you have some details about what didn't work, and what you expected to happen? |
Hi, James,
I thought it was a bug as the script worked perfectly in v.0.10... I upgraded terraform to v.0.11.1 and the topic and que will not accept the time parameters....
According to the terraform docs, the time format is supposed to be like so.... but, version 0.11 doesn't seem to like it...
(https://www.terraform.io/docs/providers/azurerm/r/servicebus_queue.html#timespan-format)
I can't seem to set the TTL value for the service bus as version 0.11 doesn't like anything I give it... 😞
resource "azurerm_servicebus_queue" "k8s_dev1_sb_que" {
name = "k8s-dev1-sb-que"
resource_group_name = "${azurerm_resource_group.k8s-dev1-rg.name}"
namespace_name = "${azurerm_servicebus_namespace.k8s_dev1_sb.name}"
requires_duplicate_detection = "False"
default_message_ttl = "00:30:00"
duplicate_detection_history_time_window = "00:15:00"
enable_partitioning = true
}
resource "azurerm_servicebus_topic" "k8s_dev1_sb_topic" {
name = "k8s-dev1-sb-topic"
resource_group_name = "${azurerm_resource_group.k8s-dev1-rg.name}"
namespace_name = "${azurerm_servicebus_namespace.k8s_dev1_sb.name}"
enable_partitioning = true
default_message_ttl = "00:30:00"
duplicate_detection_history_time_window = "00:15:00"
}
Hope this helps clarify...
Ta,
Lane
…________________________________
From: James Bardin <[email protected]>
Sent: December 19, 2017 1:58 PM
To: hashicorp/terraform
Cc: Mr. E; Mention
Subject: Re: [hashicorp/terraform] time parameter (#16950)
Hi @LaneEnglot<https://github.com/laneenglot>,
Sorry, I'm not sure what the question is here exactly. I expect this might be an azurerm provider related issue, but do you have some details about what did work, and what you expected to happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#16950 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZ8JQS6NomGZLL6TNtbT72RsmY44ewqdks5tB8EIgaJpZM4RGvzO>.
|
@LaneEnglot, |
so the exact error output of the script is:
Error: Error applying plan:
10 error(s) occurred:
* azurerm_servicebus_topic.k8s_sit_sb_topic: 1 error(s) occurred:
* azurerm_servicebus_topic.k8s_sit_sb_topic: servicebus.TopicsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: 4aeed7c0-4897-44b4-ba6d-2705f1a54b75"
* azurerm_servicebus_queue.k8s_dev1_sb_que: 1 error(s) occurred:
* azurerm_servicebus_queue.k8s_dev1_sb_que: servicebus.QueuesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: c659f859-44c3-4906-87d2-0f94491178f0"
* azurerm_servicebus_topic.k8s_ukbeta_sb_topic: 1 error(s) occurred:
* azurerm_servicebus_topic.k8s_ukbeta_sb_topic: servicebus.TopicsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: dc8e0b5b-a7cc-4075-869f-b6720bc8ea4e"
* azurerm_servicebus_topic.k8s_dev1_sb_topic: 1 error(s) occurred:
* azurerm_servicebus_topic.k8s_dev1_sb_topic: servicebus.TopicsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: 9253b1e6-c2a9-47b5-983e-02b58fd4f66e"
* azurerm_servicebus_queue.k8s_ukbeta_sb_que: 1 error(s) occurred:
* azurerm_servicebus_queue.k8s_ukbeta_sb_que: servicebus.QueuesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: 3e5e04a7-a78b-4b5c-bb9a-1bd09ad28c46"
* azurerm_servicebus_topic.k8s_uat_sb_topic: 1 error(s) occurred:
* azurerm_servicebus_topic.k8s_uat_sb_topic: servicebus.TopicsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: c373c6d0-83f5-450d-b230-a433a19ce4c6"
* azurerm_servicebus_queue.k8s_prod_sb_que: 1 error(s) occurred:
* azurerm_servicebus_queue.k8s_prod_sb_que: servicebus.QueuesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: c8ebaf91-a626-4e6a-8b9b-695ee49459c4"
* azurerm_servicebus_topic.k8s_prod_sb_topic: 1 error(s) occurred:
* azurerm_servicebus_topic.k8s_prod_sb_topic: servicebus.TopicsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: 2cce6500-1b52-42a3-b336-943588e162e4"
* azurerm_servicebus_queue.k8s_uat_sb_que: 1 error(s) occurred:
* azurerm_servicebus_queue.k8s_uat_sb_que: servicebus.QueuesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: e3205de9-51d8-4406-8f70-6314e1888237"
* azurerm_servicebus_queue.k8s_sit_sb_que: 1 error(s) occurred:
* azurerm_servicebus_queue.k8s_sit_sb_que: servicebus.QueuesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The string '00:30:00' is not a valid TimeSpan value. CorrelationId: 1e9d6deb-8c91-49a4-bf51-553e7085b86d"
I will check if the provider version changed from the upgrade...
…________________________________
From: James Bardin <[email protected]>
Sent: December 19, 2017 2:32 PM
To: hashicorp/terraform
Cc: Mr. E; Mention
Subject: Re: [hashicorp/terraform] time parameter (#16950)
@LaneEnglot<https://github.com/laneenglot>,
What exactly is the error you're receiving?
Is this with the same version of the azurerm provider under both versions of Terraform?
Does this work differently with the current version of the azurerm provider?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#16950 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZ8JQQoeFIqZjpe2ykTm-AbglEhv21zWks5tB8kAgaJpZM4RGvzO>.
|
Hi,
After mucking about with it... it seems that the provider has changed...
+ provider.azurerm v0.3.0
+ provider.azurerm v1.0.0
~~~~~
MacBook-Pro:terraform laneenglot$ terraform init
Initializing provider plugins...
The following providers do not have any version constraints in configuration,
so the latest version was installed.
To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.
* provider.azurerm: version = "~> 1.0"
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Bye for now,
Lane
…________________________________
From: Mr. Englot
Sent: December 19, 2017 2:05 PM
To: hashicorp/terraform
Subject: Re: [hashicorp/terraform] time parameter (#16950)
Hi, James,
I thought it was a bug as the script worked perfectly in v.0.10... I upgraded terraform to v.0.11.1 and the topic and que will not accept the time parameters....
According to the terraform docs, the time format is supposed to be like so.... but, version 0.11 doesn't seem to like it...
(https://www.terraform.io/docs/providers/azurerm/r/servicebus_queue.html#timespan-format)
I can't seem to set the TTL value for the service bus as version 0.11 doesn't like anything I give it... 😞
resource "azurerm_servicebus_queue" "k8s_dev1_sb_que" {
name = "k8s-dev1-sb-que"
resource_group_name = "${azurerm_resource_group.k8s-dev1-rg.name}"
namespace_name = "${azurerm_servicebus_namespace.k8s_dev1_sb.name}"
requires_duplicate_detection = "False"
default_message_ttl = "00:30:00"
duplicate_detection_history_time_window = "00:15:00"
enable_partitioning = true
}
resource "azurerm_servicebus_topic" "k8s_dev1_sb_topic" {
name = "k8s-dev1-sb-topic"
resource_group_name = "${azurerm_resource_group.k8s-dev1-rg.name}"
namespace_name = "${azurerm_servicebus_namespace.k8s_dev1_sb.name}"
enable_partitioning = true
default_message_ttl = "00:30:00"
duplicate_detection_history_time_window = "00:15:00"
}
Hope this helps clarify...
Ta,
Lane
________________________________
From: James Bardin <[email protected]>
Sent: December 19, 2017 1:58 PM
To: hashicorp/terraform
Cc: Mr. E; Mention
Subject: Re: [hashicorp/terraform] time parameter (#16950)
Hi @LaneEnglot<https://github.com/laneenglot>,
Sorry, I'm not sure what the question is here exactly. I expect this might be an azurerm provider related issue, but do you have some details about what did work, and what you expected to happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#16950 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZ8JQS6NomGZLL6TNtbT72RsmY44ewqdks5tB8EIgaJpZM4RGvzO>.
|
Seems like you've tracked down the reason for the change. |
Yes, the bug still exists.... Where do I open the bug stuff? is the azure provider under the terraform repo?
Bye for now,
Lane
…________________________________
From: James Bardin <[email protected]>
Sent: December 21, 2017 12:04 AM
To: hashicorp/terraform
Cc: Mr. E; Mention
Subject: Re: [hashicorp/terraform] time parameter (#16950)
Seems like you've tracked down the reason for the change.
We can reopen this under the azure provider is there still is an outstanding bug.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#16950 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZ8JQcDRiqLv4Hmm_ML63wwOGeajGlYuks5tCaCDgaJpZM4RGvzO>.
|
@LaneEnglot, OK. This error is coming from the Azure API. I'm not sure if there's a mismatch in the documentation and what the API expects, or a bug the client libraries. I'll move the issue over to the Azure provider where they can check it out. |
I edited your issue to include the added error output and note about the regression. |
This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#646 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know. |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Terraform Version
Terraform Configuration Files
Output
Expected Behavior
Terraform should have created the que and topic with the correct ttl values...
Actual Behavior
This worked in in .0.10.x, I upgraded and it will not accept the values for TTL.
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
terraform init
terraform apply
The text was updated successfully, but these errors were encountered: