No registration happens on vagrant up after host reboot

[mmalina]

When you have a running vagrant box (cdk) and then you restart your machine, your vagrant box will appear in a strange state.
In my case it will be aborted:

$ vagrant status
Current machine states:
default aborted (virtualbox)

This is because apparently when I go for shutdown in OS X, virtualbox will simply kill the VMs.

When I then do "vagrant up", cdk starts again, but there will be no registration happening.
(When I then do "vagrant halt" and "vagrant up", registration will happen again.)

But even if I just do ACPI Shutdown in VirtualBox, the machine state will be stopped, but on a consequent "vagrant up", there will be no registration. All the other things that usually happen on "vagrant up" will happen.

Even when no registration happens during "vagrant up", the subscription manager still returns this:

$ sudo subscription-manager status
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Current

So maybe it's all good and it's actually still registered because it was not unregistered during shutdown? In that case this issue can be simply closed. But I wanted to be sure.

This was first spotted by @mlabuda as he regularly shuts down his laptop when leaving the office for the day. Very often he doesn't think to "vagrant halt" first.

[praveenkumar]

@mmalina This issue is regarding registration plugin https:// github.com/projectatomic/adb-vagrant-registration please file it there. (I will close it here once it filled to correct repo)

[mmalina]

@praveenkumar ok, sorry about that. I created a new issue here:
projectatomic/adb-vagrant-registration#75

[praveenkumar]

Thanks @mmalina . Closing this issue.