Skip to content
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

google_compute_interconnect_attachment: error when passign mtu #8721

Closed
imrannayer opened this issue Mar 18, 2021 · 9 comments
Closed

google_compute_interconnect_attachment: error when passign mtu #8721

imrannayer opened this issue Mar 18, 2021 · 9 comments
Assignees
Labels

Comments

@imrannayer
Copy link

imrannayer commented Mar 18, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Terraform v0.13.6

  • provider registry.terraform.io/hashicorp/google v3.60.0
  • provider registry.terraform.io/hashicorp/google-beta v3.60.0

Affected Resource(s)

  • google_compute_interconnect_attachment

Terraform Configuration Files

variable "mtu" {
  type        = string
  description = "Maximum Transmission Unit (MTU), in bytes, of packets passing through this interconnect attachment. Currently, only 1440 and 1500 are allowed. If not specified, the value will default to 1440"
  default = "1440"
}

resource "google_compute_interconnect_attachment" "interconnect_attachment1_region2" {
  name    = "vl-${var.vpc_name}-${var.region1}-${local.suffix3}"
  project = local.interconnect_project_id
  region  = var.region2
  router  = var.region2_router1_name
  mtu = var.mtu

  type                     = "PARTNER"
  edge_availability_domain = "AVAILABILITY_DOMAIN_1"

  lifecycle {
    ignore_changes = ["vlan_tag8021q"]
  }
}

Debug Output

Panic Output

Expected Behavior

Create attachment

Attachment created by also getting following error:

Error: Error waiting for InterconnectAttachment "vl-vpc-us-east4-cr5" to be provisioned: "Error reading InterconnectAttachment: mtu: '' expected type 'string', got unconvertible type 'float64'"

  1. terraform apply

Important Factoids

References

  • #0000
@ghost ghost added the bug label Mar 18, 2021
@edwardmedia edwardmedia self-assigned this Mar 18, 2021
@edwardmedia
Copy link
Contributor

#8707

@edwardmedia
Copy link
Contributor

@imrannayer can you share the debug log?

@edwardmedia
Copy link
Contributor

@imrannayer is this still an issue?

@imrannayer
Copy link
Author

Yes it is still happening. I cant generate logs from my production environment and I dont have any non-prod env available at the moment.
It is happening even if I change the values from GCP GUI console after which terraform will start throwing that error.

@ghost ghost removed waiting-response labels Mar 22, 2021
@edwardmedia
Copy link
Contributor

edwardmedia commented Mar 22, 2021

@imrannayer from the error you posted, it complains the data type of that field. Currently mtu is defined as a string. I have had a fix (see #8707) . For that, you can either provide it with a string value or wait for the fix in the release. Sorry about the inconvenience

@imrannayer
Copy link
Author

I provided it as a string and it is still an issue.

@ghost ghost removed the waiting-response label Mar 22, 2021
@imrannayer
Copy link
Author

It causes a problem even if I change it from gui console after which terraform refresh keep failing with the error.

@edwardmedia
Copy link
Contributor

edwardmedia commented Mar 22, 2021

@imrannayer let's wait for the next release then. I'm closing this issue now. Feel free to raise the issue after the fix is released.

@ghost
Copy link

ghost commented Apr 22, 2021

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 22, 2021
@github-actions github-actions bot added forward/review In review; remove label to forward service/compute-interconnect labels Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants