[Vagrant 2.2.16] [1.8.9] hostmanager doesn't run before "up"; needs to run before vagrant-registration plugin #287
Description
It looks like hostmanager doesn't run before "up" (anymore?).
When doing "vagrant up" on a RHEL 8 vagrant box, I noticed that hostmanager didn't update host and guest hosts files before the vagrant-registration plugin tries to register the VM with RedHat subcription-manager. Which may be bad (I don't really know) because at that point the hostname is not "known" and thus the machine is registered as "localhost.localdomain" and not as "dev-redhat".
This only caused concern because of some other error which I am not even sure anymore if that is caused by any of this:
==> dev-redhat: Registering box with vagrant-registration...
Runtime Error HTTP Request failed: java.net.UnknownHostException: terms.api.redhat.com at java.net.InetAddress$CacedAddresses.get:797
Registering to: subscription.rhsm.redhat.com:443/subscription The system has been registered with ID: 6098cd56-32b-4aaa-894f-7ec8b8666cac The registered system name is: localhost.localdomain Installed Product Current Status: Prouct Name: Red Hat Enterprise Linux for x86_64 Status: Not Subscribed Unable to find available subscriptions for al your installed products.
Maybe this error is caused by too many registrations? Or by misregistering the same machine as two names? Like I wrote, I don't know if those two events are even related.
When doing a destroy, the order is correct, though (unregister the machine, then remove the host entries).