-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minion producing two set of keys on provision #63321
Comments
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
Possible duplicate: #62968 |
Thanks James (@OrangeDog ), looks like a PR was merged for 3006.0, any idea if there are plans to backport? #63030 |
Bug fixes do not get backports. |
I feared that, thank you. |
Recently upgraded from v2019.2 to v3004.2 and
Noticing an issue after provisioning with Salt-Cloud, causing there to be two public keys for the newly provisioned minion when I run salt-key command. One public key is accepted and is shown when first provisioning. The other is within denied and seems to show right at the completion of the provisioning. This does not allow me to send commands to the minion.
When looking at the pki directory on the salt minion I found that there were two different directories and they seem to both contain the public keys that are causing the conflict.
Removing the key from the master and restarting the service, seems to correct the issue, but does not leave a great experience when provisioning 20+ minions at a time
Command run for provisioning: sudo salt-cloud -m [redacted]-50-asc-map -P
Setup
Can provide any config if believed to be relevant, I did attempt to find a key that was associated with the minions pki location, but was not able to when looking at documentation.
Versions Report
Salt Version:
Salt: 3004.2
Dependency Versions:
cffi: Not Installed
cherrypy: unknown
dateutil: 2.8.2
docker-py: Not Installed
gitdb: 2.0.6
gitpython: 3.0.7
Jinja2: 3.1.2
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: 3.16.0
pygit2: Not Installed
Python: 3.8.10 (default, Nov 14 2022, 12:59:47)
python-gnupg: 0.4.5
PyYAML: 5.3.1
PyZMQ: 18.1.1
smmap: 2.0.5
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.2
System Versions:
dist: ubuntu 20.04 focal
locale: utf-8
machine: x86_64
release: 5.15.0-1022-aws
system: Linux
version: Ubuntu 20.04 focal
The text was updated successfully, but these errors were encountered: