-
Notifications
You must be signed in to change notification settings - Fork 202
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
Labels
Comments
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) |
Yeah, I can definitely repro this locally - working on a change now |
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
Confirmed, kitchen tries to hit the internal ip address now instead of the public one. Waiting for SSH service on 172.31.12.37 |
tyler-ball
added a commit
that referenced
this issue
Jun 8, 2015
Query correct instance object for hostname fixes #148
tyler-ball
added a commit
to chef/chef
that referenced
this issue
Jun 8, 2015
…been fixed, travis should no longer break
This was referenced Jun 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@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.
The text was updated successfully, but these errors were encountered: