Bug 30224

Thank you for the report.

Confirmed it: vagrant-2.2.9-1.mga8
Installing it involved 35 pkgs, many ruby- ones, but not 'ruby-vagrant_cloud'.

 $ vagrant init
Traceback (most recent call last):
	13: from /usr/share/vagrant/gems/bin/vagrant:23:in `<main>'
...
	 1: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- vagrant_cloud (LoadError)

Installed ruby-vagrant_cloud, then:
 $ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.

 $ urpmq --requires vagrant | grep _cloud
 $
 $ urpmq -- whatrequires ruby-vagrant_cloud
 $
No dependency either way.

Assigning this to NicolasL who looks after this SRPM.

Severity: minor => normal
Assignee: bugsquad => mageia

does installing ruby-vagrant_cloud fixes the issue for you ?

(In reply to Nicolas Lécureuil from comment #2)
> does installing ruby-vagrant_cloud fixes the issue for you ?

Yes, it does. Installing ruby-vagrant_cloud package resolves the error when calling "vagrant init", just as Lewis reported.

ok. Fixing this way then :-)

New package just pushed on the BS


src:
    - vagrant-2.2.9-1.1.mga8

Assignee: mageia => qa-bugs

mga8, x64
Installed vagrant and verified the need for ruby-vagrant_cloud by running
$ vagrant init.
Updated the package, drawing in the dependency.
$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ ll Vagrantfile
-rw-r--r-- 1 lcl lcl 3010 Apr  2 15:13 Vagrantfile

The contents of Vagrantfile do not mean much to me and it looks like a long haul to get to grips with it so this goes out on the basis that the init command does run.

$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'base' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'base' (v0) for provider: virtualbox
    default: Downloading: base
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Couldn't open file /home/lcl/base

CC: (none) => tarazed25
Whiteboard: (none) => MGA8-64-OK

(In reply to Len Lawrence from comment #6)

Thank you for your report, Lawrence! 

I sincerely apologise if you already know this; but the error is not related to this package, as it is an expected behaviour when running "vagrant up" without specifying the box to run. This stackoverflow post[1] just tells what's wrong, so your report verifies that both "vagrant init" and "vagrant run" completely work under given conditions.

[1]: (https://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up)

Yes, thanks Ryo Nagata.  I understood that - thought that it would help to try the initial commands.  Glad that it did.

Validating.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0047.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED