[BUG] - Windows minions keys are not added properly using salt-cloud creation in salt-cloud 3005.1-3 - multiple effect of this

[infantvin]

Description
Fresh install of salt 3005 latest version on RHEL9 master. Version of salt-master/cloud and salt rpm package is 3005.1-3.el9.x86_64

Creating a Windows VM using salt-cloud command and a map file. Fresh install of Windows. No additional software on it.

Post the salt-cloud -m filename windows-hostname command

All the information regarding the minion appears and then a startup state which normally runs never works.

On investigation, I see that the salt-key command shows a key for the newly setup minion in both accepted in denied

Example below:

salt-key -L

Accepted Keys:
aaa
gve-ip-w2022.xxx.com
aaaa
...
Denied Keys:
gve-ip-w2022.xxx.com

This prevents all communication between the master and minion and it fails to run any states or any salt commands in general

Setup

The salt-minion used here is the latest version listed here
https://repo.saltproject.io/windows/
Specifically the version and file is Salt-Minion-3005.1-4-Py3-AMD64-Setup.exe

Please be as specific as possible and give set-up details.

• on-prem machine
• VM (Virtualbox, KVM, etc. please specify)
• VM running on a cloud service, please be explicit and add details
• container (Kubernetes, Docker, containerd, etc. please specify)
• or a combination, please be explicit
• jails if it is FreeBSD
• classic packaging
• onedir packaging
• used bootstrap to install - I think the script is called as part of salt-cloud command framework

Steps to Reproduce the behavior
(Include debug logs if possible and relevant)

1. create a new salt master in RHEL9 include salt-cloud packages

2. Download the package for Windows and dump in root directory of master

3. create the VMware provider config and add a startup state so that it is run inside Windows when the minion comes up
   minion:
   startup_states: 'sls'
   environment: base
   sls_list:

   • ** Any state to run here**

4. create a profile for Windows 2022 server and add this line
   win_installer: /root/Salt-Minion-3005.1-4-Py3-AMD64-Setup.exe

5. create the minion of Windows 2022 using the standard salt-cloud command to create it

6. Indefinite wait time and the startup state never runs.

7. salt-key -L and you will see the accepted and denied keys for the minion which is incorrect

I cannot see any logs in the standard C:\salt\var\log\salt\minion file as that path is not created in the 3005.1 version. So no idea where to look for logs here on the minion

Expected behavior

1. The minion starts up and the defined state runs correctly on startup
2. The salt-key -L is showing the key as accepted and not as denied or both (which seems to be incorrect)
3. Logs are present in C:\salt\var.. path location as normal.

Screenshots

I will add a screenshot in the next step.

Versions Report

salt --versions-report

output from masters putty session. The minion version report I have attached a screenshot # salt-master --versions-report Salt Version: Salt: 3005.1

Dependency Versions:
cffi: 1.14.6
cherrypy: 18.6.1
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.0
libgit2: 1.5.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.21
pycrypto: 3.16.0
pycryptodome: 3.9.8
pygit2: 1.11.1
Python: 3.9.16 (main, Nov 1 2022, 00:00:00)
python-gnupg: 0.4.8
PyYAML: 5.4.1
PyZMQ: 23.2.0
smmap: Not Installed
timelib: 0.2.4
Tornado: 4.5.3
ZMQ: 4.3.4

System Versions:
dist: rhel 9.1 Plow
locale: utf-8
machine: x86_64
release: 5.14.0-162.6.1.el9_1.x86_64
system: Linux
version: Red Hat Enterprise Linux 9.1 Plow

Additional context

Seems to be multiple problems here. Please ask me if you have any questions.

[infantvin]

I have added as many details as I can. Please ask me if you need any more information

[OrangeDog]

Duplicate: #62968