Admin network issue with VirtualBox on Tumbleweed

[GarySmith]

I followed the directions to ensure that there was no pre-existing vboxnet0 network defined in VirtualBox. Yet when vagrant up gets to the first controller node, it dies with the error message:
==> controller1: Defined interface to use (eth1) does not seem to be on the admin network.
==> controller1: Is DHCP used for it?

Noteworthy: after it died, I went into the VirtualBox UI and found that the VirtualBox vboxnet0 network had been created, with a DHCP server whose address server address and upper/lower address range were all in the wrong range 192.168.56 (I think it was) instead of 192.168.124, which is what the crowbar_register script expects.

I don't really know crowbar, so here's what I did to get the cloud up and running:

• In the VirtualBox settings, I changed the DHCP server and range to the 192.168.124 address
• In the crowbar_register script on the admin node (in /srv/tftpboot/suse-12.2./x86_64) I commented out the logic that does the checks and has the error about "Is DHCP used for it?"
• one at a time I did a vagrant up of each of the remaining 4 vagrant boxes. For some bizarre reason, the crowbar_register script on the admin node would get overwritten with the original contents during each 'vagrant up', so I had to keep replacing it with my modified version after each box was started.

Now, this was all an ugly hack, but it did get SOC 7 up, and I was able run crowbar and apply all of the cloud barclamps successfully.