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

SSH failures after port 22 is open because user doesn't exist yet #106

Closed
adrienverge opened this issue Sep 24, 2014 · 0 comments · Fixed by #139
Closed

SSH failures after port 22 is open because user doesn't exist yet #106

adrienverge opened this issue Sep 24, 2014 · 0 comments · Fixed by #139
Assignees
Milestone

Comments

@adrienverge
Copy link

Some cloud distros create users account with delay. In the meantime, SSH becomes available (i.e. port 22 open), but it's still not possible to open an SSH connection because the user account doesn't exist yet. This results in failures at next steps (provisioning...)

Maybe you should add a check in CreateServer.call to ensure user can SSH to machine (line 69 after checking port 22).

@julienvey julienvey added the bug label Sep 24, 2014
@julienvey julienvey added this to the 0.5 milestone Sep 24, 2014
@julienvey julienvey self-assigned this Sep 25, 2014
@julienvey julienvey removed their assignment Oct 3, 2014
@ggiamarchi ggiamarchi self-assigned this Oct 12, 2014
@julienvey julienvey added the SSH label Oct 16, 2014
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants