Bug 1196537 - plugins won't install in local user's home with new vagrant 1.7.2 RPMs
Summary: plugins won't install in local user's home with new vagrant 1.7.2 RPMs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-26 08:27 UTC by Casey
Modified: 2015-11-26 09:32 UTC (History)
6 users (show)

Fixed In Version: vagrant-1.7.2-3.fc21.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 10:26:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Casey 2015-02-26 08:27:41 UTC

Comment 1 Casey 2015-02-26 08:30:18 UTC
[Ugh, sorry I hit RETURN prematurely. Here is the bug report]


As mentioned in bug #1196188, vagrant plugin install can't install plugins as the local user.

$ vagrant plugin install vagrant-hostsupdater

Errno::EPERM: Operation not permitted @ chmod_internal - /usr/share/vagrant/bin/vagrant

Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

An error occurred while installing vagrant (1.7.2), and Bundler cannot continue.
Make sure that `gem install vagrant -v '1.7.2'` succeeds before bundling.

Using sudo installs them to /root/.vagrant.d/

Comment 2 Casey 2015-02-26 08:30:36 UTC
[Ugh, sorry I hit RETURN prematurely. Here is the bug report]


As mentioned in bug #1196188, vagrant plugin install can't install plugins as the local user.

$ vagrant plugin install vagrant-hostsupdater

Errno::EPERM: Operation not permitted @ chmod_internal - /usr/share/vagrant/bin/vagrant

Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

An error occurred while installing vagrant (1.7.2), and Bundler cannot continue.
Make sure that `gem install vagrant -v '1.7.2'` succeeds before bundling.

Using sudo installs them to /root/.vagrant.d/

Comment 3 Michael Adam 2015-02-26 08:35:44 UTC
confirmed.
Thanks for reporting!

Comment 4 Vít Ondruch 2015-02-26 08:46:43 UTC
This is just F21 issue IMO, since on F22, there is already incorporated this [1] patch in RubyGems. In other words, the patches.rb file *just for F21 and older fedoras* should look like the one in one of my original submissions [2].


[1] https://github.com/rubygems/rubygems/commit/8ebe03e075a32a67bee0643089d69bf20a910ac1
[2] http://people.redhat.com/vondruch/vagrant-1.6.5-14.fc22.src.rpm

Comment 5 Michael Adam 2015-02-26 09:04:46 UTC
(In reply to Vít Ondruch from comment #4)
> This is just F21 issue IMO, since on F22, there is already incorporated this
> [1] patch in RubyGems. In other words, the patches.rb file *just for F21 and
> older fedoras* should look like the one in one of my original submissions
> [2].
> 
> 
> [1]
> https://github.com/rubygems/rubygems/commit/
> 8ebe03e075a32a67bee0643089d69bf20a910ac1
> [2] http://people.redhat.com/vondruch/vagrant-1.6.5-14.fc22.src.rpm

Ok... Thanks for your hints!
Are you saying that the cause of the problem
lies outside of vagrant itself and that we should undo
the change that the commit 15c0557a2220d7b2000cb5f8a6b83f968b60ca1e
"Initial import (#1020456)." has done to patches.rb?

Michael

Comment 6 Vít Ondruch 2015-02-26 09:08:32 UTC
(In reply to Michael Adam from comment #5)
> (In reply to Vít Ondruch from comment #4)
> > This is just F21 issue IMO, since on F22, there is already incorporated this
> > [1] patch in RubyGems. In other words, the patches.rb file *just for F21 and
> > older fedoras* should look like the one in one of my original submissions
> > [2].
> > 
> > 
> > [1]
> > https://github.com/rubygems/rubygems/commit/
> > 8ebe03e075a32a67bee0643089d69bf20a910ac1
> > [2] http://people.redhat.com/vondruch/vagrant-1.6.5-14.fc22.src.rpm
> 
> Ok... Thanks for your hints!
> Are you saying that the cause of the problem
> lies outside of vagrant itself and that we should undo
> the change that the commit 15c0557a2220d7b2000cb5f8a6b83f968b60ca1e
> "Initial import (#1020456)." has done to patches.rb?

Exactly, but just for F21 and older.

> 
> Michael

Comment 7 Michael Adam 2015-02-26 09:16:37 UTC
(In reply to Vít Ondruch from comment #6)
> (In reply to Michael Adam from comment #5)
> > (In reply to Vít Ondruch from comment #4)
> > > This is just F21 issue IMO, since on F22, there is already incorporated this
> > > [1] patch in RubyGems. In other words, the patches.rb file *just for F21 and
> > > older fedoras* should look like the one in one of my original submissions
> > > [2].
> > > 
> > > 
> > > [1]
> > > https://github.com/rubygems/rubygems/commit/
> > > 8ebe03e075a32a67bee0643089d69bf20a910ac1
> > > [2] http://people.redhat.com/vondruch/vagrant-1.6.5-14.fc22.src.rpm
> > 
> > Ok... Thanks for your hints!
> > Are you saying that the cause of the problem
> > lies outside of vagrant itself and that we should undo
> > the change that the commit 15c0557a2220d7b2000cb5f8a6b83f968b60ca1e
> > "Initial import (#1020456)." has done to patches.rb?
> 
> Exactly, but just for F21 and older.

Understood.
Also I can confirm that it fixes the issue!

Going to file an update... Thanks for the hint!

Comment 8 Fedora Update System 2015-02-26 10:02:22 UTC
vagrant-1.7.2-3.a.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/vagrant-1.7.2-3.a.fc21

Comment 9 Fedora Update System 2015-02-27 09:24:15 UTC
Package vagrant-1.7.2-3.a.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing vagrant-1.7.2-3.a.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-2716/vagrant-1.7.2-3.a.fc21
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2015-02-28 10:26:50 UTC
vagrant-1.7.2-3.a.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2015-03-03 16:58:37 UTC
vagrant-1.7.2-3.fc21.1 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/vagrant-1.7.2-3.fc21.1

Comment 12 Fedora Update System 2015-03-05 12:35:18 UTC
vagrant-1.7.2-3.fc21.1 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 brandon feldkamp 2015-11-25 14:17:13 UTC
I'm seeing a nearly identical issue on F23 with installing vagrant-hostmanager and I can't seem to track down the root cause of my issue. 

I installed the latest vagrant via 'dnf install vagrant' (version 1.7.4).

and when I execute 'vagrant plugin install vagrant-hostmanager' I get the following output:

Installing the 'vagrant-hostmanager' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

An error occurred while installing vagrant (1.7.4), and Bundler cannot continue.
Make sure that `gem install vagrant -v '1.7.4'` succeeds before bundling.

Errno::EPERM: Operation not permitted @ chmod_internal - /usr/share/vagrant/bin/vagrant

Any ideas?

Comment 14 brandon feldkamp 2015-11-25 14:25:36 UTC
Just rolled back to Vagrant 1.7.3 and it worked.

Comment 15 Josef Stribny 2015-11-26 09:32:18 UTC
Brandon,

I don't think its the same issue. So please file a new bug if this is still problem.

If I install @vagrant group and run vagrant plugin install vagrant-hostmanager it works for me.

If you are about to report the issue please include the exact vagrant RPM version and exact steps made on a fresh system so I can reproduce. Thanks.

> Just rolled back to Vagrant 1.7.3 and it worked.

Strange as we never had 1.7.3 in Fedora[0]. So that's upstream RPM?



[0] http://koji.fedoraproject.org/koji/packageinfo?packageID=19808


Note You need to log in before you can comment on or make changes to this bug.