salt: Salt-cloud create EC2 instance but failed to deploy salt-minion, but minion-key appear in salt-master
Description of Issue/Question
Problem 1 : salt-cloud create EC2 instance and accept salt-minion key from no where even no salt-minion package deployed on the instance
I use salt-cloud command to create EC2 instance using my own profile
sudo salt-cloud -p "new-app" mywebserver
Instance successfully created, I also notice a key name of mywebserver appear inside salt-key. But test.ping. After ssh inside the server , I notice no salt-minion deployed on mywebserver.
Problem 2 : saltify failed even after delete the minion-key(that don’t know where it came from) from salt-key.
# so I delete the key of the minion , since there is no package installed.
sudo salt-key -d mywebserver
# then I try to saltify it
sudo salt-cloud -p "saltify-my-web" mywebserver
it just show me this kinda error
mywebserver:
----------
Error:
mywebserver already exists under my-aws:ec2
Where my-aws:ec2 is my cloud provider . HOWEVER, there is no such entry of mywebserver inside my cloud.profiles.d
I just issue IP address and saltify just run through without issues. e.g.
sudo salt-cloud -p "saltify-my-web" 172.16.100.22
Versions Report
Salt Version:
Salt: 2015.8.8.2
Dependency Versions:
Apache Libcloud: 0.15.1
Jinja2: 2.7.2
M2Crypto: Not Installed
Mako: 0.9.1
PyYAML: 3.10
PyZMQ: 14.0.1
Python: 2.7.6 (default, Jun 22 2015, 17:58:13)
RAET: Not Installed
Tornado: 4.2.1
ZMQ: 4.0.4
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.5.1
gitdb: 0.5.4
gitpython: 0.3.2 RC1
ioflo: Not Installed
libgit2: Not Installed
libnacl: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.3.0
mysql-python: 1.2.3
pycparser: Not Installed
pycrypto: 2.6.1
pygit2: Not Installed
python-gnupg: Not Installed
smmap: 0.8.2
timelib: Not Installed
System Versions:
dist: Ubuntu 14.04 trusty
machine: x86_64
release: 3.13.0-74-generic
system: Ubuntu 14.04 trusty
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 17 (6 by maintainers)
@commutecat, @johje349 has confirmed the fix on the 2015.8 branch, so I think we are good to close.
@commutecat, thanks for confirming. Do you think this issue could be closed?
The problem was introduced by commit a743778e98796d98181ad94f7cbebee20546def2. Most likely because config.py moved to a separate directory in the develop branch.
It was later fixed by commit 5a9f4e947e906c5ac5d3b06e0c59298e66abb271.
So the workaround is to update /usr/lib/python2.7/dist-packages/salt/config.py on the salt-master until a release with the fix arrives.