What causes "Saving box information..." in hashicorp/vagrant?

Treat the line as expected output; publish continues automatically after the save completes.

Saving box information...

Error message

Saving box information...

What it means

Progress notice from `vagrant cloud publish` (plugins/commands/cloud/publish.rb) printed via ui.warn but purely informational: after applying box/version/provider attribute updates it announces 'Saving box information...' and calls box.save, which PUTs the whole box state to Vagrant Cloud. It then proceeds to optional box-file upload and release steps.

Source

Thrown at plugins/commands/cloud/publish.rb:114

          end

          # Load up all the models we'll need to publish the asset
          box = load_box(org, box_name, @client.token)
          box_v = load_box_version(box, version)
          box_p = load_version_provider(box_v, provider_name, params[:architecture])

          # Update all the data
          set_box_info(box, params.slice(:private, :short_description, :description))
          set_version_info(box_v, params.slice(:version_description))
          set_provider_info(box_p, params.slice(
            :architecture,
            :checksum,
            :checksum_type,
            :default_architecture,
            :url))

          # Save any updated state
          @env.ui.warn(I18n.t("cloud_command.publish.box_save"))
          box.save

          # If we have a box file asset, upload it
          if box_file
            upload_box_file(box_p, box_file, options.slice(:direct_upload))
          end

          # If configured to release the box, release it
          if options[:release] && !box_v.released?
            release_version(box_v)
          end

          # And we're done!
          @env.ui.success(I18n.t("cloud_command.publish.complete", org: org, box_name: box_name))
          format_box_results(box_p, @env)
          0
        rescue VagrantCloud::Error => err
          @env.ui.error(I18n.t("cloud_command.errors.publish.fail", org: org, box_name: box_name))

View on GitHub (pinned to 35f3160f4a)

Solutions

Treat the line as expected output; publish continues automatically after the save completes.
If the step seems hung, check network/proxy to app.vagrantup.com rather than the message itself.
Keep CI log parsers keyed on the final 'Complete! Published org/box' success line instead of this intermediate warn.
If save fails, the surrounding error handling surfaces a VagrantCloud error with the HTTP cause — act on that, not this notice.

Defensive patterns

Strategy: validation

Prevention

Treat 'Saving box information...' as normal progress, not an error condition.
Key CI success detection on the final 'Complete! Published' line or the command exit status.
Set generous timeouts around publish for large descriptions/slow links; the pause after this line is the save round-trip.

When it happens

Trigger: Any `vagrant cloud publish org/box v p file.box ...` run that reaches the save phase — i.e. box and version/provider objects were created or loaded and mutated; the message appears right before the network round-trip that persists them.

Common situations: Users misreading the warn channel as an error in CI logs; long pauses after the message on slow links while box.save transmits; re-publishing over an existing box where save overwrites descriptions/providers.

Related errors

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