Skip to content

Plugin initialisation tells users to expunge but ignores local plugins #13029

Open
@tomjn

Description

@tomjn

If a user updates vagrant, then vagrant plugins will have incorrect dependencies and need to expunge.

Unfortunately, the command suggested does not have --local so users who have local vagrant plugins who try to use the suggested command will complain that it does not work.

Expected behavior

The output should include a --local parameter so that the command fixes things for everybody, not just those who stick to global plugins only

Actual behavior

The output does not include a --local parameter

Reproduction information

Vagrant version

All versions of vagrant ruby

Host operating system

All Operating systems

Guest operating system

All guests

Steps to reproduce

  1. install a vagrant plugin with --local
  2. update vagrant
  3. try to vagrant up and recieve error message
  4. try to use the recommended expunge command
  5. local plugins are not expunged and user is unaware that --local is needed to fix the problem

Vagrantfile

# all vagrant files are affected, contents of vagrant file are irrelevant

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions