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

provider/aws: Invalid protocol aws_network_acl_rule #12103

Closed
MattiasGees opened this issue Feb 20, 2017 · 2 comments
Closed

provider/aws: Invalid protocol aws_network_acl_rule #12103

MattiasGees opened this issue Feb 20, 2017 · 2 comments

Comments

@MattiasGees
Copy link
Contributor

Terraform Version

v0.8.7

Affected Resource(s)

  • aws_network_acl_rule

Terraform Configuration Files

resource "aws_network_acl" "nat" {
  vpc_id     = "${var.vpc_id}"
  subnet_ids = ["${var.nat_subnets}"]
}

resource "aws_network_acl_rule" "nat_ingress_vrrp_nat" {
  network_acl_id = "${aws_network_acl.nat.id}"
  rule_number    = "1110"
  egress         = false
  protocol       = 112
  rule_action    = "allow"
  cidr_block     = "10.20.20.0/24"
}

Debug Output

* aws_network_acl_rule.nat_ingress_vrrp_nat: Invalid Protocol 112 for rule 1110

Expected Behavior

That the terraform plan completes without giving any errors.

Actual Behavior

terraform plan gives errors at the end of the plan to say that 112 is an invalid protocol. While at the seem time this is saved in the terraform state file with the correct protocol. It is also correctly deployed on the AWS console
I looked it up in the protocol numbers and 112 is present in that list http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply
  2. terraform plan
@stack72
Copy link
Contributor

stack72 commented Feb 20, 2017

Closed via #12107

@ghost
Copy link

ghost commented Apr 16, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants