vagrant-box-updater: uninitialized constant Psych::ENGINE (NameError)

52 views
Skip to first unread message

Anna Gulaev

unread,
Jan 25, 2019, 1:09:32 PM1/25/19
to Vagrant
I successfully set up this box on a Windows 10 machine yesterday. On another Windows 10 machine today I am getting errors in vagrant-box-updater. Latest version of virtualbox 6.0.2, latest version of vagrant 2.2.3.

This is what vagrant box add looks like:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dev' (v0) for provider:
    box: Downloading: https://[ommitted]
    box: Progress: 100% (Rate: 1464k/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'dev' (v0) for 'virtualbox'!
T:/boxes/gems/2.4.4/gems/vagrant-box-updater-0.0.3/lib/vagrant-box-updater/util/common.rb:7:in `get_path_box_stat_file': uninitialized constant Psych::ENGINE (NameError)
        from T:/boxes/gems/2.4.4/gems/vagrant-box-updater-0.0.3/lib/vagrant-box-updater/action/add_box.rb:27:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/box_add.rb:123:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/plugins/commands/box/command/add.rb:78:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/plugins/commands/box/command/root.rb:66:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/cli.rb:58:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:291:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:182:in `<main>'

This is what vagrant up looks like:
vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
T:/boxes/gems/2.4.4/gems/vagrant-box-updater-0.0.3/lib/vagrant-box-updater/util/common.rb:7:in `get_path_box_stat_file': uninitialized constant Psych::ENGINE (NameError)
    from T:/boxes/gems/2.4.4/gems/vagrant-box-updater-0.0.3/lib/vagrant-box-updater/action/up_box.rb:19:in `call'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:239:in `action_raw'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:208:in `block in action'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:614:in `lock'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:194:in `call'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:194:in `action'
    from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

Process finished with exit code 1

Anna Gulaev

unread,
Jan 25, 2019, 1:13:53 PM1/25/19
to Vagrant
Uninstalling vagrant-box-updater, of course, resolves this.
Reply all
Reply to author
Forward
0 new messages