vagrant-bindfs autopkgtest regression

Bug #1937076 reported by Graham Inggs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vagrant (Ubuntu)
Fix Released
Undecided
Unassigned
vagrant-bindfs (Debian)
New
Unknown
vagrant-bindfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

The autopkgtests of vagrant-bindfs/1.1.5-1 have regressed in release.
Version 1.1.6-1 in Debian fails with a different message.

autopkgtest [00:28:24]: test smoke-test: [-----------------------
Vagrant failed to initialize at a very early stage:

The plugins failed to initialize correctly. This may be due to manual
modifications made within the Vagrant home directory. Vagrant can
attempt to automatically correct this issue by running:

  vagrant plugin repair

If Vagrant was recently updated, this error may be due to incompatible
versions of dependencies. To fix this problem please remove and re-install
all plugins. Vagrant can attempt to do this automatically by running:

  vagrant plugin expunge --reinstall

Or you may want to try updating the installed plugins to their latest
versions:

  vagrant plugin update

Error message given during initialization: undefined method `request' for nil:NilClass
autopkgtest [00:28:24]: test smoke-test: -----------------------]
smoke-test FAIL non-zero exit status 1

Revision history for this message
Graham Inggs (ginggs) wrote :

Currently, this prevents the migration of vagrant/2.2.14+dfsg-1ubuntu1 from -proposed.

Graham Inggs (ginggs)
Changed in vagrant (Ubuntu):
status: New → Fix Released
Changed in vagrant-bindfs (Debian):
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.