[Bug]: apache could not be loaded
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?
After upgrading from 3006 to 3008.2, I experience this with apache_* states:
----------
ID: ssl
Function: apache_module.enabled
Result: False
Comment: State 'apache_module.enabled' was not found in SLS 'ssl.httpd'
Reason: 'apache_module' __virtual__ returned False: apache module could not be loaded
Changes:
I noticed depreciation of the module for 3009+, but in 3008 this should continue to work.
Even with -l trace, I see no reason why the module fails.
The apache packages are installed, and the helpers (like a2ensite, apache2ctl etc.) are present.
Type of salt install
Official deb
Major version
3008.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)
debian-13
(corrected values, dropdown list did not contain them)
salt --versions-report output
Salt Version:
Salt: 3008.2
Python Version:
Python: 3.14.6 (main, Jun 11 2026, 02:19:05) [GCC 11.2.0]
Dependency Versions:
cffi: 2.0.0
cherrypy: 18.10.0
cryptography: 48.0.0
dateutil: 2.9.0.post0
docker-py: Not Installed
gitdb: 4.0.12
gitpython: 3.1.50
Jinja2: 3.1.6
libgit2: Not Installed
looseversion: 1.3.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.1.2
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 24.0
pycparser: 3.00
pycrypto: Not Installed
pycryptodome: 3.23.0
pygit2: Not Installed
python-gnupg: 0.5.6
PyYAML: 6.0.3
PyZMQ: 27.1.0
relenv: 0.22.14
smmap: 5.0.2
timelib: 0.3.0
Tornado: 6.5.7
ZMQ: 4.3.5
Salt Package Information:
Package Type: onedir
System Versions:
dist: debian 13.5 trixie
locale: utf-8
machine: x86_64
release: 6.12.95+deb13-amd64
system: Linux
version: Debian GNU/Linux 13.5 trixie
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 apache_module.enabled entry point and reproduce the failure on Debian 13 with Salt 3008.2, using the provided apache packages and helper commands. Trace why the apache module is unavailable despite those helpers being present, then verify that apache_* states load successfully and the reported state can run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100