Update vagrant_box_version to >= 201801.02.0

[tangrufus]

Follow up on #938

Issues with box version should be very rare.
During the past 6 months of using Trellis, I never encountered any issues with box version. Besides, when provisioning production servers, we can't control which server image the hosting company provides. Trellis should work as long as it's ubuntu 16.04.

[swalkinshaw]

I agree 👏

[mockey]

@swalkinshaw, @tangrufus
The thing is I don't get any update mesages with this anymore, even if my version is lower.
It even seems to disable the update check.
With vagrant_box_version: '<= 201801.02.0' I get:

==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: A newer version of the box 'bento/ubuntu-16.04' for provider 'virtualbox' is
==> default: available! You currently have version '201710.25.0'. The latest is version
==> default: '201801.02.0'. Run `vagrant box update` to update.

With vagrant_box_version: '>= 201801.02.0' I get none of this.
BTW: Current version is: 201805.15.0

[tangrufus]

Not sure why box automatic update checking doesn't kick in. I found a issue about bento/ubuntu-16.04's tagging:

Version 201805.15.0 is listed on https://app.vagrantup.com/bento/boxes/ubuntu-16.04. But vagrant box update doesn't pick up 201805.15.0.

➜ vagrant box update
==> default: Checking for updates to 'bento/ubuntu-16.04'
    default: Latest installed version: 201803.24.0
    default: Version constraints: >= 201801.02.0
    default: Provider: virtualbox
==> default: Box 'bento/ubuntu-16.04' (v201803.24.0) is running the latest version.

➜ vagrant version
Installed Version: 2.1.1
Latest Version: 2.1.1

You're running an up-to-date version of Vagrant!

Maybe related:

• VirtualBox Graphical User Interface
  Version 5.2.12 r122591 (Qt5.6.3)
• macOS High Sierra
  Version 10.13.4

[mockey]

vagrant box update doesn't pick up 201805.15.0

Confirmed. That's weird.
Vagrant 2.1.1 here as well (on Linux Mint 17.3)

[mockey]

vagrant box update doesn't pick up 201805.15.0

@tangrufus:
There is a new version v201806.08.0 available now, which isn't picked up as well.
Only v201803.24.0 is marked as the currently released version. Maybe that's why newer versions don't get picked?

[mockey]

As far as I see, >= just doesn't work for updating an older version, just like specifying the version without <= doesn't work. vagrant box update returns:
==> default: Box 'bento/ubuntu-16.04' not installed, can't check for updates.
if the version is higher than the installed one

[tangrufus]

Box update checking resumes to work for me:

With vagrant_box_version: '>= 201801.02.0':

➜ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'bento/ubuntu-16.04'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: A newer version of the box 'bento/ubuntu-16.04' for provider 'virtualbox' is
==> default: available! You currently have version '201803.24.0'. The latest is version
==> default: '201806.08.0'. Run `vagrant box update` to update.

Besides, $ vagrant box update now works as expected.

[mockey]

Yes, I saw that, too. 201806.08.0 is now labelled currently released version .
Update worked for me as well.
Maybe I got it wrong because there were newer version that were not released. I don't know...
Thanks for checking anyway.