 | 1 | initial version |
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.
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.