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.

Sign up for GitHub

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

Jump to bottom

vagrant ssh {master,minion-1} does not work #4633

Closed
jameskyle opened this issue Feb 20, 2015 · 2 comments
Closed

vagrant ssh {master,minion-1} does not work #4633

jameskyle opened this issue Feb 20, 2015 · 2 comments
Labels
area/platform/vagrant kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@jameskyle
Copy link
Contributor

The Vagrantfile requires that ENV['KUBE_TEMP'] is set. If it is not, any vagrant command will fail as the file cannot be parsed. The error received is:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

shell provisioner:
* `path` for shell provisioner does not exist on the host system: /master-start.sh

This is contrary to the suggested method of interaction in the documentation found at https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/vagrant.md which says:

To access the master or any minion:

    vagrant ssh master
    vagrant ssh minion-1
@jameskyle
Copy link
Contributor Author

Looking at the scripts, this temp directory is set on script run and cleaned up on EXIT by a trap.

I've wrapped a conditional around the provision statement which allows the other commands to work, but outputs a warning that the vm will not have a provisioner set.

Pull req incoming.

@derekwaynecarr
Copy link
Member

Cc me on your PR and I will review. I have been swamped on other topics so it's possible something regressed.

@vmarmol vmarmol added area/platform/vagrant kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 20, 2015
vmarmol added a commit that referenced this issue Feb 20, 2015
@vmarmol
Merge pull request #4636 from jameskyle/feature/vagrant-up-fix-4633
2575c45 
Resolves #4633.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/platform/vagrant kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jameskyle @vmarmol @derekwaynecarr