vagrant-registration does not work in conjunction with the vagrant-vbguest plugin

[hferentschik]

When a user has the vbguest plugin installed the startup of the VM won't work. The vbguest plugin seems to run prior to the registration plugin and tries to run a yum command. This will lead to an error like this:

==> default: Machine booted and ready!
No installation found.
Loaded plugins: product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
There are no enabled repos.
 Run "yum repolist all" to see the repos you have.
 You can enable repos with yum-config-manager --enable <repo>
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default: 
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

yum install -y kernel-devel-`uname -r` gcc make perl bzip2

Stdout from the command:

Loaded plugins: product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.


Stderr from the command:

There are no enabled repos.
 Run "yum repolist all" to see the repos you have.
 You can enable repos with yum-config-manager --enable <repo>

As a workaround one can set config.vbguest.auto_update = false.

I don't know whether there is a way to ensure a specific order in plugin execution, but it might be at least worth documenting.

[strzibny]

Good point, I will look at this.

[strzibny]

Just as a reference, this is a Stack Overflow question:
http://stackoverflow.com/questions/31610801/how-can-i-define-the-run-order-of-vagrant-middleware-plugins

[strzibny]

This is now implemented by #46.

[hferentschik]

@strzibny This should work with vagrant-registration (1.1.0) right? We had this issue reported - redhat-developer-tooling/openshift-vagrant#48

[strzibny]

@hferentschik yes, see CHANGELOG https://github.com/pvalena/adb-vagrant-registration/blob/master/CHANGELOG.md#110

[LalatenduMohanty]

Closing this as #69 is opened to track this.