hashicorp/vagrant · warning

This will revoke version %{version} from %{box} from Vagrant

Error message

This will revoke version %{version} from %{box} from Vagrant Cloud. This cannot be undone.

What it means

Safety warning printed by `vagrant cloud version revoke` before it pulls a released box version back from Vagrant Cloud, which cannot be undone. Shown only when --force is absent; the shared continue prompt then gates the revoke, and any answer other than "y" returns exit code 1.

Source

Thrown at plugins/commands/cloud/version/revoke.rb:37

              o.separator "Revokes a version entry on Vagrant Cloud"
              o.separator ""
              o.separator "Options:"
              o.separator ""
              o.on("-f", "--[no-]force", "Force revocation without confirmation") do |f|
                options[:force] = f
              end
            end

            # Parse the options
            argv = parse_options(opts)
            return if !argv
            if argv.size != 2
              raise Vagrant::Errors::CLIInvalidUsage,
                help: opts.help.chomp
            end

            if !options[:force]
              @env.ui.warn(I18n.t("cloud_command.version.revoke_warn", version: argv[1], box: argv.first))
              cont = @env.ui.ask(I18n.t("cloud_command.continue"))
              return 1 if cont.strip.downcase != "y"
            end

            @client = client_login(@env)
            org, box_name = argv.first.split('/', 2)
            version = argv[1]

            revoke_version(org, box_name, version, @client.token, options)
          end

          # Revoke release of box version
          #
          # @param [String] org Organization name
          # @param [String] box_name Box name
          # @param [String] version Version of the box
          # @param [String] access_token User Vagrant Cloud access token
          # @param [Hash] options Currently unused

View on GitHub (pinned to 35f3160f4a)

Solutions

1. Answer `y` at the prompt to revoke the release
2. Use `--force` in scripts to revoke without prompting
3. Answer anything but `y` to abort (exit code 1, version still released)
4. Confirm the target version with `vagrant cloud box info org/box` before running

Example fix

# before
vagrant cloud version revoke acme/app 1.0.0   # interactive prompt
# after (automation)
vagrant cloud version revoke acme/app 1.0.0 --force

# Preflight: confirm the version is currently released before revoking
vagrant cloud box info acme/app | grep -A2 "1.0.0"

When it happens

Trigger: `vagrant cloud version revoke org/box 1.2.3` without --force, after argv parses as exactly ["org/box", version]. A non-y answer aborts with exit code 1 and the version stays released.

Common situations: Pulling back a bad or leaked version; scripted revocation hitting the interactive prompt; uncertainty because revocation is irreversible.

Related errors

• This will completely remove version %{version} from %{box} f
• This will release version %{version} from %{box} to Vagrant
• The format of box version provided (%{version}) is incorrect
• A version of the box you're loading is formatted in a way th
• The Vagrant app data directory (%{path}) is in a structure V

AI-assisted analysis of hashicorp/vagrant@35f3160f4a (2026-08-21). Data as JSON: /api/errors/16f49d8eab49aa35. Report an issue: GitHub.