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

You broke Chef's Travis CI tests =) #148

Closed
lamont-granquist opened this issue Jun 4, 2015 · 3 comments · Fixed by #151
Closed

You broke Chef's Travis CI tests =) #148

lamont-granquist opened this issue Jun 4, 2015 · 3 comments · Fixed by #151
Assignees
Labels

Comments

@lamont-granquist
Copy link
Contributor

@tyler-ball check out:

https://travis-ci.org/chef/chef/jobs/65344115

After the kitchen-ec2 release yesterday TK started trying to hit the private 172.x IPaddr of the virt rather than the public IP.

@lamont-granquist
Copy link
Contributor Author

About all I can see is 02dc5b4 which by factoring out wait_until_ready() I think you may have lost the side effects which updated the server and hostname variables in the scope of create(state)

@tyler-ball
Copy link
Contributor

Yeah, I can definitely repro this locally - working on a change now

@tyler-ball tyler-ball self-assigned this Jun 4, 2015
tyler-ball added a commit that referenced this issue Jun 4, 2015
…nection information instead of the new object we queried to make sure it is ready, fixes #148
tyler-ball added a commit that referenced this issue Jun 4, 2015
…nection information instead of the new object we queried to make sure it is ready, fixes #148
tyler-ball added a commit that referenced this issue Jun 4, 2015
…nection information instead of the new object we queried to make sure it is ready, fixes #148
@scarolan
Copy link
Contributor

scarolan commented Jun 8, 2015

Confirmed, kitchen tries to hit the internal ip address now instead of the public one.

Waiting for SSH service on 172.31.12.37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants