Open kees-closed opened 1 year ago
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. Please be sure to review our Code of Conduct. Also, check out some of our community resources including:
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. If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!
Most networking states don't work properly on most current OS versions.
See also: #13085, #54791
In RHEL8, and now RHEL9, you should be using NetworkManager manage network configuration. NM can handle the old network-scripts. See https://github.com/saltstack/salt/issues/54791#issuecomment-641332362
You could work around the unmaintained network.managed
state module by using file.managed
to generate the config files, which will work on 7/8/9, and then cmd.run
to invoke nmcli
to reload and activate networks.
In RHEL8, and now RHEL9, you should be using NetworkManager manage network configuration. NM can handle the old network-scripts. See #54791 (comment)
You could work around the unmaintained
network.managed
state module by usingfile.managed
to generate the config files, which will work on 7/8/9, and thencmd.run
to invokenmcli
to reload and activate networks.
It's possible to install network-scripts, but wouldn't it be much better if Salt supports what RHEL officially supports? I don't really want to install the deprecated network-scripts.
Description I want to add a route on a RHEL8.4 system, instead I get a failure about that network.service is not found on RHEL8. I can't find this network.service in the Salt code (quick searches via GitHub). I also don't see how I can override this behavior. It is also quite strange that it does this, as if the OS is not detected properly, or that the wrong conditional is triggered, or that simply the wrong service is called. The documentation also doesn't include more info about it: https://docs.saltproject.io/en/master/ref/states/all/salt.states.network.html#salt.states.network.routes
Setup (Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Please be as specific as possible and give set-up details.
Steps to Reproduce the behavior (Include debug logs if possible and relevant)
The salt state I run.
Expected behavior I expect the route to be added and active after Salt is done.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.) ```yaml Salt Version: Salt: 3004.1 Dependency Versions: cffi: 1.11.5 cherrypy: Not Installed dateutil: 2.6.1 docker-py: Not Installed gitdb: Not Installed gitpython: Not Installed Jinja2: 2.10.1 libgit2: 0.26.8 M2Crypto: 0.35.2 Mako: Not Installed msgpack: 0.6.2 msgpack-pure: Not Installed mysql-python: Not Installed pycparser: 2.14 pycrypto: Not Installed pycryptodome: 3.9.7 pygit2: 0.26.4 Python: 3.6.8 (default, Sep 9 2021, 07:49:02) python-gnupg: Not Installed PyYAML: 3.12 PyZMQ: 19.0.0 smmap: Not Installed timelib: Not Installed Tornado: 4.5.3 ZMQ: 4.3.4 System Versions: dist: rhel 8.5 Ootpa locale: UTF-8 machine: x86_64 release: 4.18.0-348.el8.x86_64 system: Linux version: Red Hat Enterprise Linux 8.5 Ootpa ```Additional context Add any other context about the problem here.