VirtualBox Script unable to manage interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining |
Bug Description
Detailed bug description:
The VirtualBox scripts for Fuel 9.0 are failing when running the launch.sh script with the following configuration:
-Windows 7
-VirtualBox 5.1.18 + 5.1.18 Extension Pack
-Cygwin x64
-Mirantis OpenStack 9.0 + 9.0 VirtualBox Scripts
(which satisfies the requirements specified in the documentation)
Steps to reproduce:
Follow the steps exactly as outlined in:
https:/
to configure VirtualBox and cygwin.
Expected results:
launch.sh script runs successfully without any errors, proceeds to configuration of VirtualBox VMs
Actual result:
When running the launch script (for either launch.sh, launch_8GB.sh, or launch_16GB.sh), the following error is shown:
$ sh launch.sh
./functions/
Prepare the host system...
Checking for 'dumpkeys.cache'... OK
Checking for 'free'... OK
Checking for 'expect'... OK
Checking for 'xxd'... OK
Checking for 'VBoxManage'... OK
Checking for VirtualBox Extension Pack... OK
Checking for VirtualBox iPXE firmware...SKIP
VirtualBox iPXE firmware is not found. Used standard firmware from the VirtualBox Extension Pack.
Checking for Mirantis OpenStack ISO image... OK
Going to use Mirantis OpenStack ISO file: iso/MirantisOpe
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Done.
Check available memory on the host system...
Done.
Сlean previous installation if exists...
Done.
Deleting old interfaces if exists...
...eting host-only interface: VirtualBox Host-Only Ethernet Adapter
' could not be foundr: The host network interface named 'VirtualBox Host-Only Ethernet Adapter
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetwor
" was not removed. Aborting...x Host-Only Ethernet Adapter
Reproducibility:
100%. This issue was initially reported by a customer, and I was able to reproduce this in a fresh Windows 7 installation.
Workaround:
Unknown
Impact:
Unable to create virtualbox VMs with scripts.
Description of the environment:
Operation system: Windows 7
Versions of components:
-VirtualBox 5.1.18 + 5.1.18 Extension Pack
-Cygwin x64
-Mirantis OpenStack 9.0 + 9.0 VirtualBox Scripts
(which satisfies the requirements specified in the documentation)
Reference architecture: N/A
Network model: N/A
Related projects installed: N/A
Additional information:
Based on the error message indicating that it could not delete the Host-Only Ethernet Adapter, I edited the config.sh file and set the following parameter:
rm_network=0
and now we can see that it fails to create a new one when re-launching the script:
$ sh launch.sh
./functions/
Prepare the host system...
Checking for 'dumpkeys.cache'... OK
Checking for 'free'... OK
Checking for 'expect'... OK
Checking for 'xxd'... OK
Checking for 'VBoxManage'... OK
Checking for VirtualBox Extension Pack... OK
Checking for VirtualBox iPXE firmware...SKIP
VirtualBox iPXE firmware is not found. Used standard firmware from the VirtualBox Extension Pack.
Checking for Mirantis OpenStack ISO image... OK
Going to use Mirantis OpenStack ISO file: iso/MirantisOpe
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Done.
Check available memory on the host system...
Done.
Сlean previous installation if exists...
Done.
Deleting old interfaces if exists...
Done.
Creating host-only interface...
0%...10%
Fatal error. Interface VirtualBox Host-Only Ethernet Adapter #2 does not exist after creation. Exiting
Changed in fuel: | |
milestone: | none → 9.x-updates |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Even i am also facing the same issue. Any work around available ?