VirtualBox Scripts for MOS 6.1 do not work with VirtualBox 5.0.4 on Windows 10/8.1

Bug #1497425 reported by Javier Diaz Jr
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Opinion
Wishlist
Fuel Documentation Team
6.1.x
Won't Fix
Wishlist
MOS Maintenance
7.0.x
Won't Fix
Wishlist
MOS Maintenance

Bug Description

More details in ticket: https://mirantis.zendesk.com/agent/tickets/8496

Reported via customer:

Gentlemen, to update - I seem to have found the issue. It seems that VirtualBox 5.0.4 will not allow the FUEL Scripts to execute in either Windows 10 or in Windows 8.1

I have downgraded Virtualbox to VirtualBox 4.3.28 and it works great now.

Also, Windows 10 seems to interfer regardless of using VirtualBox 4.3.28 build. Since all new desktops come now with Windows 10. I recommend a bug report. Is there a URL where I can fill out to report the issues with 5.3 of Virtualbox and also with Windows 10? Windows 8.1 is being phased out by OEM Vendors - so we need to tackle this issue.

Revision history for this message
Mike Scherbakov (mihgen) wrote :

QA team, can you please clarify what versions of vbox we've certified as working for Fuel 6.1 ?
We may need to change documentation. It has to explicitly say which version is supported.

Changed in fuel:
assignee: nobody → Fuel QA Team (fuel-qa)
milestone: none → 8.0
Revision history for this message
Anastasia Palkina (apalkina) wrote :

I am testing on Ubuntu on VBox version 4.3.30

Changed in fuel:
importance: Undecided → Wishlist
status: New → Invalid
status: Invalid → Opinion
Revision history for this message
John Devereaux (jdevereaux) wrote :

Anastasia, good morning - can you also put into your testing roadmap using Windows 10 and 8.1 with VirtualBox 5.0.4 for Windows hosts? New PCs are now coming out with Windows 10 and Microsoft also is giving every Windows 7 and Windows 8 customers the option to upgrade to Windows 10 for free. So this will be a repeatable issue pertaining to using Virtualbox 6.1 scripts with VirtualBox 5.0.4 ( the latest version).

Thank you.

JD

Roman Rufanov (rrufanov)
tags: added: customer-found support
no longer affects: fuel/6.0.x
Revision history for this message
Roman Rufanov (rrufanov) wrote :

customer found on MOS 6.1 and Virtualbox build # 5.0.4 Windows 10 64bit with error:
RROR: Unable to fetch url 'http://archive.ubuntu.com/ubuntu/', error 'Network is unreachable - connect(2)'. Please verify node connectivity to this URL, or remove it from the settings page if it is invalid. on node node-6.domain.tld

Revision history for this message
Miroslav Anashkin (manashkin) wrote :

So far I use VirtualBox 5.0.x without issues under Linux only.
Under Windows I continue using VirtualBox 4.3.x, since 5.0 under Windows looks too buggy.

Revision history for this message
Vlad Okhrimenko (vokhrimenko) wrote :

Today, I have tested scripts with VirtualBox 5.0.4 under Windows 8.1, and got same error. I think it's bug in VirtualBox. Please look this https://www.virtualbox.org/ticket/14040. Despite the fact that ticket was fixed -- some people continue to observe this bug (and I'm too). After I downgraded the VirtualBox version (VirtualBox 5.0.0) -- scripts are working good

tags: added: release-notes
Revision history for this message
Artem Hrechanychenko (agrechanichenko) wrote :

Verified on 5.0.6 VirtualBox
New issue with checking vboxnet0 interface
https://bugs.launchpad.net/fuel/+bug/1505582

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-qa
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

If we don't support virtual box installations on Win 8/10, I think we have to document at least.

Changed in fuel:
status: Confirmed → Opinion
assignee: Fuel QA Team (fuel-qa) → nobody
assignee: nobody → Fuel Documentation Team (fuel-docs)
tags: added: wontfix-low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.