New Question
0

The system cannot find the drive specified

asked 2016-09-15 23:49:04 +0300

ADarkDividedGem gravatar image

updated 2016-09-16 12:42:47 +0300

At the end of the V-Magine installation it installs OpenStack Hyper-V Computer Mitaka which in turn returns the following error message within an alert box:

The system cannot find the drive specified

Everything else installed fine but because of this error V-Magine reports that the "OpenStack deployment failed". Any idea what went wrong and how to fix it?

The full nova_install.logcan be downloaded here: https://log-files-openstack-v-magine....

edit retag flag offensive close merge delete

Comments

In the v-magine directory, there's a nova_install.log file. Can you please share it?

alexpilotti gravatar imagealexpilotti ( 2016-09-16 11:35:42 +0300 )edit

I have uploaded the nova_install.log file to an Amazon S3 Storage bucket and shared the link above. Hope that helps.

ADarkDividedGem gravatar imageADarkDividedGem ( 2016-09-16 12:44:28 +0300 )edit

Thanks for the log. Here's the relevant error, this happens when restarting the nova-compute service: http://paste.openstack.org/show/579313/. In order to try to reproduce the issue, what Windows version and build are you using?

alexpilotti gravatar imagealexpilotti ( 2016-09-16 13:17:12 +0300 )edit

I am using Microsoft Hyper-V Server 2012 R2 (Version Major: 6 | Minor: 3 | Build: 9600 | Revision: 0)

ADarkDividedGem gravatar imageADarkDividedGem ( 2016-09-16 13:49:22 +0300 )edit

Thanks for the details. Some more questions that could help: is the instance fully updated (Windows updates)? Do you have an antivirus running?

alexpilotti gravatar imagealexpilotti ( 2016-09-16 14:08:54 +0300 )edit

1 answer

Sort by » oldest newest most voted
1

answered 2016-09-16 22:24:42 +0300

alexpilotti gravatar image

Managed to reproduce the issue, here's how the Mitaka MSI is called (changed the username):

msiexec /i HyperVNovaCompute_Mitaka_13_0_0.msi /l*v ADDLOCAL=HyperVNovaCompute,NeutronHyperVAgent,iSCSISWInitiator,FreeRDP NEUTRONADMINTENANTNAME=services RPCBACKENDPORT=5672 USECOWIMAGES=1 GLANCEPORT=9292 DYNAMICMEMORYRATIO=1 CONFIGDRIVEINJECTPASSWORD=1 GLANCEHOST=10.63.167.3 NEUTRONURL=http://10.63.167.3:9696 ADDVSWITCH=0 NEUTRONADMINPASSWORD=********** INSTANCESPATH=C:\OpenStack\Instances RPCBACKEND=RabbitMQ NOVACOMPUTESERVICEPASSWORD=******** NEUTRONADMINAUTHURL=http://10.63.167.3:35357/v3 RDPCONSOLEURL=http://HV1:8000 ENABLELOGGING=1 NOVACOMPUTESERVICEUSER=HV1\UsernameChanged NEUTRONADMINUSERNAME=neutron VSWITCHNAME=v-magine-data FORCECONFIGDRIVE=1 LOGDIR=C:\OpenStack\Log RPCBACKENDHOST=10.63.167.3 VERBOSELOGGING=1 /qb /l*v c:\log.txt

If the NOVACOMPUTESERVICEPASSWORD has characters like e.g. =,", etc, this might not be recognized properly by the msiexec escaping, resulting in the service not starting due to a wrong password.

The resulting error is a "service user not found" error that unfortunately Windows translates in a very misleading "The system cannot find the drive specified".

We're currently testing a fix for this issue.

edit flag offensive delete link more

Comments

Thanks, this explains why when I tried to start the "OpenStack Nova Compute Service" it returned "Error 1069: The service did not start due to a logon failure.". After updating the Log On details for the service it started successfully.

ADarkDividedGem gravatar imageADarkDividedGem ( 2016-09-16 22:40:06 +0300 )edit

Fix has been released in version 2016.1.0.2, thanks!

alexpilotti gravatar imagealexpilotti ( 2016-09-17 13:41:32 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower

Stats

Asked: 2016-09-15 23:49:04 +0300

Seen: 69 times

Last updated: Sep 16 '16