Skip to content

/ saltfs

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

Jump to bottom

Vagrant on Linux failing to load due to permission error with the minon file? #238

Closed
larsbergstrom opened this issue Mar 8, 2016 · 4 comments
Closed

Vagrant on Linux failing to load due to permission error with the minon file? #238

larsbergstrom opened this issue Mar 8, 2016 · 4 comments

Comments

@larsbergstrom
Copy link
Contributor

@larsbergstrom larsbergstrom commented Mar 8, 2016

@aneeshusa Do you have any idea why this might be failing when I attempt to vagrant up a new machine and how to fix it?

Copying salt minion config to /etc/salt
Failed to upload a file to the guest VM via SCP due to a permissions
error. This is normally because the SSH user doesn't have permission
to write to the destination location. Alternately, the user running
Vagrant on the host machine may not have permission to read the file.

Source: /home/larsberg/saltfs/.travis/minion
Dest: /etc/salt/minion
[larsberg@thor saltfs]$
@larsbergstrom
Copy link
Contributor Author

@larsbergstrom larsbergstrom commented Mar 8, 2016

Aha! Looks like this is a problem with newer Vagrants:
hashicorp/vagrant#5973
@larsbergstrom
Copy link
Contributor Author

@larsbergstrom larsbergstrom commented Mar 8, 2016

s/newer/older. Ubuntu installs 1.7.4 Vagrant, but #180 moved us to 1.8.0. So this is user error on my part!
@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Mar 8, 2016

Thanks for updating the wiki, I totally meant to add that after the PR landed but forgot! This bug was definitely a thorn in the side for a while.
@larsbergstrom
Copy link
Contributor Author

@larsbergstrom larsbergstrom commented Mar 8, 2016

No problem! It was actually somewhat fortunate, as I wasn't in a huge rush today and it forced me to learn a lot about how Vagrant works :-)
aneeshusa added a commit to aneeshusa/servo-saltfs that referenced this issue Mar 8, 2016
@aneeshusa
Ensure Vagrant version is at least 1.8.0
77a7a7a 
Use the Vagrant.require_version helper documented here:
https://www.vagrantup.com/docs/vagrantfile/vagrant_version.html

Eliminates issues like servo#238.
@aneeshusa aneeshusa mentioned this issue Mar 8, 2016
Merged
bors-servo added a commit that referenced this issue Mar 24, 2016
@bors-servo
Auto merge of #240 - aneeshusa:ensure-minimum-vagrant-version, r=lars…
Loading status checks…
c1d73d7 
…bergstrom

Ensure Vagrant version is at least 1.8.0

Use the Vagrant.require_version helper documented here:
https://www.vagrantup.com/docs/vagrantfile/vagrant_version.html

Eliminates issues like #238.

Heads up: I didn't test this with a Vagrant older than 1.8.0, so I have no idea if this actually works.
@larsbergstrom can you test this if possible since you ran into this?
I want to make sure this is actually a useful change.

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/240)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@larsbergstrom @aneeshusa
You can’t perform that action at this time.