Closed null0000 closed 9 years ago
Thanks for this report @null0000.
ping @techhat and @erjohnso
Oh, also @null0000 can you please provide the output of salt-cloud --versions-report
?
Here you go:
Salt Version: Salt: 2015.2.0rc2-5001-ged6eadc
Dependency Versions: Apache Libcloud: 0.17.1-dev Jinja2: 2.6 M2Crypto: 0.21.1 Mako: Not Installed PyYAML: 3.10 PyZMQ: 13.1.0 Python: 2.7.3 (default, Mar 13 2014, 11:03:55) RAET: Not Installed ZMQ: 3.2.3 ioflo: Not Installed libnacl: Not Installed msgpack-pure: Not Installed msgpack-python: 0.1.10 pycrypto: 2.6
System Versions: dist: debian 7.8 machine: x86_64 release: 3.16.0-0.bpo.4-amd64 system: debian 7.8
@null0000 - this looks to be a problem with the GCE image itself and not related to salt. I can repro the issue just using stock GCE Ubuntu-14.x VMs from my laptop.
Given the provided cloud.profiles, clean.map, and master files, ubuntu fails to start with the error:
Modifying the profile for clean-vm1 to use the debian-7 image makes the salt-cloud command succeed
Ubuntu images on GCE doesn't allow "root@" access via ssh, so the problem part of that line is:
The environment configuration is pretty much identical to the setup found in the gce demonstration except for changes listed, and I ran:
without the "v2014.1.10" option passed to the install script. I'm also using the head revision of apache libcloud's gce.py file.
/etc/salt/master:
/etc/salt/cloud.profiles:
/etc/salt/clean.map:
I also modified the gce-config provider (/etc/salt/cloud) according to the instructions in the aforementioned gce quickstart guide.
To reproduce: sudo salt-cloud -P -y -m /etc/clean.map
debug.out: