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

DHCP Option Set weirdness #210

Closed
c4milo opened this issue Apr 29, 2015 · 8 comments
Closed

DHCP Option Set weirdness #210

c4milo opened this issue Apr 29, 2015 · 8 comments
Labels
guidance Question that needs advice or information.

Comments

@c4milo
Copy link

c4milo commented Apr 29, 2015

I can't really tell whether this is a problem with the Go API, the AWS service itself or Ubuntu's resolvconf version. I have this Terraform branch where I'm setting multiple domain-name-servers it seems to work fine and checking the AWS Console I can see the options appear to be set correctly:

However, when I spin up an EC2 instance using the VPC with the above DHCP Options, this is what I get in my /etc/resolv.conf file:

Does anyone have any idea of what might be going on here?

Thanks for the help!

@lsegal
Copy link
Contributor

lsegal commented Apr 29, 2015

@c4milo can you provide the code that you are using with the SDK that is causing this issue? I will say that if the service is accepting your request with a 200 successful response, it's unlikely that the SDK is the cause of any issues here-- this looks like a configuration issue with an EC2 instance itself. You can also verify that the SDK is sending the correct request by enabling logging (LogLevel: 1 in the service constructor).

@c4milo
Copy link
Author

c4milo commented Apr 29, 2015

@c4milo can you provide the code that you are using with the SDK that is causing this issue?

I provided the link to the section of the code involved above but here it goes again: https://github.com/managedbyq/terraform-1/blob/aws_dhcp_options/builtin/providers/aws/resource_aws_vpc_dhcp_options.go#L85-L95

I will say that if the service is accepting your request with a 200 successful response, it's unlikely that the SDK is the cause of any issues here--

Yes, the response is 200 and what it is creating can be seen in the screenshot I originally posted above.

this looks like a configuration issue with an EC2 instance itself.

The configuration looks OK to me. The EC2 instance is using the VPC that has associated the involved DHCP Option Set.

You can also verify that the SDK is sending the correct request by enabling logging (LogLevel: 1 in the service constructor).

I will look into this. Thanks!

@lsegal
Copy link
Contributor

lsegal commented Apr 30, 2015

@c4milo it looks like you are using the SDK correctly, but you may not be using the API correctly (i.e. sending the right values to EC2). I'm not entirely sure what your intended goal is, but this doesn't look like a problem with the SDK unless you can show wire logs of incorrect data being sent to the service.

@lsegal lsegal added guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Apr 30, 2015
@c4milo
Copy link
Author

c4milo commented Apr 30, 2015

@c4milo it looks like you are using the SDK correctly, but you may not be using the API correctly (i.e. sending the right values to EC2)

What values should I be sending? I tried sending only one value with a string containing the list of name servers and it didn't work either.

I'm not entirely sure what your intended goal is, but this doesn't look like a problem with the SDK unless you can show wire logs of incorrect data being sent to the service.

Unfortunately, I ran out of time chasing this issue. I'm going to close this for now and re-open it later if it makes sense.

@c4milo c4milo closed this as completed Apr 30, 2015
@pikeas
Copy link

pikeas commented Jun 28, 2015

@c4milo This issue is linked from www.terraform.io/docs/providers/aws/r/vpc_dhcp_options.html. Is this still a problem, or did you resolve it? If there's still a problem, could you please link to the new open issue?

@c4milo
Copy link
Author

c4milo commented Jun 28, 2015

It's ok from the SDK side, dhclient is just too weird.

@pikeas
Copy link

pikeas commented Jun 28, 2015

I'm not sure what that means - is there currently an issue in Terraform, or was it resolved?

@c4milo
Copy link
Author

c4milo commented Jun 28, 2015

There is no issue in Terraform.
On Sun, Jun 28, 2015 at 5:01 PM Aris Pikeas [email protected]
wrote:

I'm not sure what that means - is there currently an issue in Terraform,
or was it resolved?


Reply to this email directly or view it on GitHub
#210 (comment).

@diehlaws diehlaws removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance Question that needs advice or information.
Projects
None yet
Development

No branches or pull requests

4 participants