[BUG] Onboarding failed (salt error)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
When attempting to register a minion at a remote site, registration fails with an email:
"Error registering minion id: " (_note: the salt key is accepted, but the states do not apply
_)
Running '/usr/lib/venv-salt-minion/bin/salt-call -l debug state.apply' on the remote system results in an error:
**local:
Data failed to compile:
Specified SLS packages.packages_3a564680c9c94cba82d6a8051ca96a6b in saltenv base is not available on the salt master or through a configured fileserver
Specified SLS custom.custom_3a564680c9c94cba82d6a8051ca96a6b in saltenv base is not available on the salt master or through a configured fileserver**
I verified via /usr/bin/nc that the prospective client can reach Ports 443, 4505 and 4506, this can also be seen in tcpdump traces viewed in Wireshark.
Setup
Both the Uyuni server and the client that cannot register are Azure VMs in different regions (I am attempting to register a new server for a proxy directly with the Uyuni master server), however I am able to replicate the behavior with another host directly on the same VNET.
Steps to Reproduce the behavior
Run bootstrap script via 'curl -Ssk | bash', can re-trigger on client via 'salt-call -l debug state.apply'
Expected behavior
Registration of the new server completes.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions Report
[root@client ~]# /usr/lib/venv-salt-minion/bin/salt-call --versions-report
Salt Version:
Salt: 3006.0
Python Version:
Python: 3.11.11 (main, Feb 19 2025, 13:22:34) [GCC]
From client:
Dependency Versions:
cffi: 1.15.1
cherrypy: Not Installed
contextvars: Not Installed
dateutil: 2.8.2
docker-py: 7.0.0
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.2
libgit2: Not Installed
looseversion: 1.0.2
M2Crypto: 0.44.0
Mako: Not Installed
msgpack: 1.0.7
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 23.2
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: Not Installed
pygit2: Not Installed
python-gnupg: Not Installed
PyYAML: 6.0.1
PyZMQ: 24.0.1
relenv: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.2.3
System Versions:
dist: almalinux 9.5 Teal Serval
locale: utf-8
machine: x86_64
release: 5.14.0-503.35.1.el9_5.x86_64
system: Linux
version: AlmaLinux 9.5 Teal Serval
From server container:
Salt Version:
Salt: 3006.0
Python Version:
Python: 3.6.15 (default, Sep 23 2021, 15:41:43) [GCC]
Dependency Versions:
cffi: 1.13.2
cherrypy: unknown
contextvars: 2.4
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.10.1
libgit2: 1.7.1
looseversion: 1.0.2
M2Crypto: 0.44.0
Mako: Not Installed
msgpack: 0.5.6
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 21.3
pycparser: 2.17
pycrypto: Not Installed
pycryptodome: Not Installed
pygit2: 1.14.0
python-gnupg: Not Installed
PyYAML: 5.4.1
PyZMQ: 17.1.2
relenv: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.2.3
System Versions:
dist: sles 15.6
locale: UTF-8
machine: x86_64
release: 5.14.0-503.34.1.el9_5.x86_64
system: Linux
version: SLES 15.6
Additional context
Attached the output of the "salt-call -l debug state.apply" command.
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
Start with the attached salt_apply.txt and reproduce the failure using /usr/lib/venv-salt-minion/bin/salt-call -l debug state.apply on the client. Trace why the packages.packages_3a564680c9c94cba82d6a8051ca96a6b and custom.custom_3a564680c9c94cba82d6a8051ca96a6b SLS packages are unavailable, then verify that registration completes and the states apply.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100