Closed dacron closed 4 years ago
This issue only occurs when the IP mode of the MAAS hosts interface is set to auto assign. Setting to DHCP works fine. My understanding is that static network configuration is a feature of MAAS Cloudbase-init service.
@dacron can you provide some debug information for this issue, please?
From PowerShell:
get-service wmi*
get-service winrm
winrm id
& 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\\python.exe -m pip freeze'
@dacron Please use the latest installer (beta). The stable installer uses a component (PyMI 1.0.4 for setting networking which relies on winrm to work. This issue is fixed in PyMI and the newer PyMI version is used by the latest Cloudbase-Init installer: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msi
Here is the debug information:
PS C:\Windows\system32> Get-Service wmi*
Status Name DisplayName
------ ---- -----------
Stopped wmiApSrv WMI Performance Adapter
PS C:\Windows\system32> Get-Service winrm
Status Name DisplayName
------ ---- -----------
Running winrm Windows Remote Management (WS-Manag...
PS C:\Windows\system32> winrm id IdentifyResponse
ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 10.0.18363 SP: 0.0 Stack: 3.0
SecurityProfiles
SecurityProfileName = http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/basic, http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/basic, http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/mutual, http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/spnego-kerberos, http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/spnego-kerberos
PS C:\Windows\system32> & 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\python.exe' -m pip freeze Babel==2.8.0
certifi==2020.4.5.1
chardet==3.0.4
cloudbase-init==1.1.1
comtypes==1.1.7
debtcollector==2.0.1
dnspython==1.15.0
eventlet==0.25.2
extras==1.0.0
fixtures==3.0.0
greenlet==0.4.15
idna==2.9
iso8601==0.1.12
Jinja2==2.11.1
linecache2==1.0.0
MarkupSafe==1.1.1
monotonic==1.5
msgpack==0.6.2
netaddr==0.7.19
netifaces==0.10.9
oauthlib==3.1.0
openstack-requirements==1.2.1.dev3425
oslo.config==8.0.2
oslo.context==3.0.2
oslo.i18n==4.0.1
oslo.log==4.1.1
oslo.serialization==3.1.1
oslo.utils==4.1.1
packaging==20.3
Parsley==1.3
pbr==5.4.5
PyMI==1.0.4
pyparsing==2.4.7
pyserial==3.4
python-dateutil==2.8.1
python-mimeparse==1.6.0
pytz==2019.3
pywin32==227
PyYAML==5.3.1
requests==2.23.0
rfc3986==1.4.0
six==1.14.0
stevedore==1.32.0
testtools==2.4.0
traceback2==1.4.0
tzlocal==2.0.0
unittest2==1.1.0
untangle==1.1.1
urllib3==1.25.8
WMI==1.4.9
wrapt==1.12.1
Just building a new image with the beta installer for testing.
@dacron I see that my assumptions were correct. Let me know if the beta installer works as expected.
@ader1990 1.1.2.dev5 does fix the issue. Any idea when it will hit stable?
@dacron just release 1.1.2: https://github.com/cloudbase/cloudbase-init/releases/tag/1.1.2
Closing the issue based on your feedback, please feel free to reopen it if anything changes.
sadly 1.1.2 does not work for me, 1.1.0 works good though....
@jshen28 can you please share the logs?
Hello, I tried the latest version of cloudbase-init and try to inject IPV6 address, the same error has occured again? Could you guys provide any suggestions?
Appreciate...
sadly 1.1.2 does not work for me too, windows server 2012 r2
When deploying a Windows 10 1909 image via MAAS and Cloudbase-init 1.1.1 the network settings do not persist.
After initial MAAS deployment the deployed host is accessible. However, when the deployed host is restarted it is not reachable again. It looks like an issue with the network config plugin. Prior to restarting the host I see this in cloudbase-init.log:
Post restart the cloudbase-init.log contains:
I'm guessing that the errors in the log post-restart are a direct result of the pre-restart failure.