[Bug]: salt-cloud in 3007.9 not generating any events when run on a minion (with salt-master installed but not used)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
What happened?
I built a separate minion with salt, salt-minion, salt-cloud & salt-master 3007.9 installed on Rocky Linux 9.6. The minion is part of our MAIN salt-master with all VM's and was built to separate the salt-cloud/ VM deployment functionality away from the main salt-master. There is an extensive implementation of salt-minion events being generated now with an extensive implementation of reactors in place and working.
When creating empty DHCP/EFI VM's for booting highly custom OS images in a HPC environment, no
salt / cloud / <VM> / *
event messages are being generated (or received on the MAIN salt-master.
I have tested simulating the events from the minion using salt-call
salt-call event.send 'salt/cloud/TEST/created' profile="test-pro" provider="cli" name="sid"
local:
True
The captured event on the master using:
salt-run state.event tag='salt/cloud/*/*'
salt/cloud/TEST/created {"id": "salt-cloud-dev.our-company.edu.au", "tag": "salt/cloud/TEST/created", "data": {"profile": "test-pro", "provider": "cli", "name": "sid", "__pub_fun": "event.send", "__pub_pid": 212469, "__pub_jid": "20251202231039079379", "__pub_tgt": "salt-call"}, "cmd": "_minion_event", "ts": 1764717039, "_stamp": "2025-12-02T23:10:39.093395"}
VM is created using:
salt-cloud -p minimal testing-vm-100 -l debug
and
salt-cloud -p minimal testing-vm-100
VM is being deleted with:
salt-cloud -d testing-vm-100
Type of salt install
Official rpm
Major version
3007.x
What supported OS are you seeing the problem on? Can select multiple. (If bug appears on an unsupported OS, please open a GitHub Discussion instead)
oraclelinux-9, rockylinux-9
salt --versions-report output
# salt --versions-report
Salt Version:
Salt: 3007.9
Python Version:
Python: 3.10.19 (main, Oct 30 2025, 04:53:28) [GCC 11.2.0]
Dependency Versions:
cffi: 2.0.0
cherrypy: unknown
cryptography: 42.0.5
dateutil: 2.8.2
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.6
libgit2: Not Installed
looseversion: 1.3.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.7
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 24.0
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.19.1
pygit2: Not Installed
python-gnupg: 0.5.2
PyYAML: 6.0.1
PyZMQ: 25.1.2
relenv: 0.21.2
smmap: Not Installed
timelib: 0.3.0
Tornado: 6.5.2
ZMQ: 4.3.4
Salt Package Information:
Package Type: onedir
System Versions:
dist: rocky 9.6 Blue Onyx
locale: utf-8
machine: x86_64
release: 5.14.0-503.14.1.el9_5.x86_64
system: Linux
version: Rocky Linux 9.6 Blue Onyx
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with salt-cloud on the described minion setup, then compare its behavior with salt-call event.send and salt-run state.event using the shown event tags. Trace the salt-cloud create and delete commands to determine why events are not generated or received; done means the expected salt/cloud/ events appear on the main salt-master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100