You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying a VM from a template using the Vcenter provider, the VM gets created, but provisioning wont continue until the interface is brought up. Salt-cloud does not bring up the interface using open-vm-tools, so the VM will never recieve a IP Address.
What ive tried:
remove NIC from template, to get one with proper IP address - FAIL
have a default NIC, which is onnected at power on - Fail
like two, but have Salt create a second with correct MAC - Fail
1-3 with both VMware and OpenVM tools 6x-fail
1 but with a Centos 7 - Fail
Doing 1. but when salt-cloud is waiting on IPv4, do a manual connect on the NIC (edit settings > connnect) - Works
I have seen some issues regarding this on other Github posts here, but none specify a solution for the problem.
Theres a load of text in this issue, trying to stay ahead of the debug curve. thank you for reading through it
Setup
(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
provider for vCenter 6.7
So thats really nothing special.
The template is a Ubuntu server 18.04.3 LTS with Open-VM-Tools installed. For networking purposes i removed the network card. as i need it to have one specific network card with a specific MAC for the DHCP server to run with. Hence they are commented out. more to follow (Check the map)
And there it sits for about a half eternity before giving up.
This has been tried with both Open-VM-Tools and VMware-tools from the vCenter server itself. Both givesthe same result.
Versions Report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
root@salt:~# salt --versions-report
Salt Version:
Salt: 2019.2.0
Dependency Versions:
cffi: Not Installed
cherrypy: unknown
dateutil: 2.6.1
docker-py: Not Installed
gitdb: 2.0.4
gitpython: 2.1.11
ioflo: Not Installed
Jinja2: 2.10
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.7
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.15+ (default, Oct 2 2018, 22:12:08)
python-gnupg: 0.4.1
PyYAML: 3.12
PyZMQ: 17.1.0
RAET: Not Installed
smmap: 2.0.4
timelib: Not Installed
Tornado: 5.0.2
ZMQ: 4.2.5
System Versions:
dist: Ubuntu 18.10 cosmic
locale: UTF-8
machine: x86_64
release: 4.18.0-15-generic
system: Linux
version: Ubuntu 18.10 cosmic
The text was updated successfully, but these errors were encountered:
Looking through the VMWare.py Connector i can se that there are alot of checks to idetntify whether the NIC is connected or not, but doing any action on the status. maybe a feature request that have a function in vmware.py which will connect a NIC if it is not connected? https://puu.sh/D0fYR/704f6392da.png
Sooooo i did alot of digging around! https://kb.vmware.com/s/article/54986
what you have to do when running Ubuntu 18.04.2(3) is that they removed ifup and started using netplan and cloud-init. and the customization does occur long beofre dbus service starts, hence it cannot control VM hardware.
What worked for me
1. apt purge cloud-init -y #Dont want to see that one again!
2. comment out "/tmp 1777 root root -" from /usr/lib/tmpfiles.d/tmp.conf
3. apt install open-vm-tools
4. add "After=dbus.service" under [unit] in file /lib/systemd/system/open-vm-tools.service
Description of Issue/Question
When deploying a VM from a template using the Vcenter provider, the VM gets created, but provisioning wont continue until the interface is brought up. Salt-cloud does not bring up the interface using open-vm-tools, so the VM will never recieve a IP Address.
What ive tried:
I have seen some issues regarding this on other Github posts here, but none specify a solution for the problem.
Theres a load of text in this issue, trying to stay ahead of the debug curve. thank you for reading through it
Setup
(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
provider for vCenter 6.7
So thats really nothing special.
The template is a Ubuntu server 18.04.3 LTS with Open-VM-Tools installed. For networking purposes i removed the network card. as i need it to have one specific network card with a specific MAC for the DHCP server to run with. Hence they are commented out. more to follow (Check the map)
Here comes the map that i am using to create this specific VM
Steps to Reproduce Issue
(Include debug logs if possible and relevant.)
salt-cloud -m influx-mac.map -l debug
Wall of text:
And there it sits for about a half eternity before giving up.
This has been tried with both Open-VM-Tools and VMware-tools from the vCenter server itself. Both givesthe same result.
Versions Report
(Provided by running
salt --versions-report
. Please also mention any differences in master/minion versions.)The text was updated successfully, but these errors were encountered: