-
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
[BUG] Cannot ping windows minion because keys are under both Accepted and Denied. #63016
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 |
Not sure if this issue is related to #63024 Grains doesn't work on windows minions |
Please check the following comment |
This is a duplicate of #62968 |
Description
Windows minion deployed through cloud profile ends up in both Denied keys and Accepted keys. As a result Salt Master can't ping the newly deployed VM.
This is not a issue with Linux VM's. The keys are only under Accepted keys.
Steps to Reproduce the behavior
Deploy a Windows VM using the following profile.
salt-cloud -p azure-win2012 wintest27
After deployment the test.ping fails and check the
salt-key -L
. The new VM is under both Accepted keys and Denied keys.root@salt:~# salt-key -L
Accepted Keys:
app01
app02
wintest25
wintest26
wintest27
Denied Keys:
wintest25
wintest26
wintest27
Unaccepted Keys:
Rejected Keys:
Here is the cloud profile I'm using to deploy the VM.
cat /etc/salt/cloud.profiles.d/azure.conf:
Expected behavior
The key needs to be either in Accepted or denied. Not in both state.
Versions Report
salt --versions-report
root@salt:~# salt --versions-report
Salt Version:
Salt: 3005.1
Dependency Versions:
cffi: 1.15.1
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: 4.0.9
gitpython: 3.1.24
Jinja2: 3.0.3
libgit2: 1.1.0
M2Crypto: 0.38.0
Mako: Not Installed
msgpack: 1.0.3
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.11.0
pygit2: 1.6.1
Python: 3.10.6 (main, Aug 10 2022, 11:40:04) [GCC 11.3.0]
python-gnupg: 0.4.8
PyYAML: 5.4.1
PyZMQ: 22.3.0
smmap: 5.0.0
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: ubuntu 22.04 Jammy Jellyfish
locale: utf-8
machine: x86_64
release: 5.15.0-1022-aws
system: Linux
version: Ubuntu 22.04 Jammy Jellyfish
Additional Details
In order to ping the newly created VM, You'll need a new key. The existing keys under Accepted and Denied doesn't let you ping at all.
The text was updated successfully, but these errors were encountered: