-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CentOS 8 and networking state #54791
Comments
Debian 10 probably faces this issue as well. |
|
Also : Line 1054 in 1dc8e30
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
🤔 |
Thank you for updating this issue. It is no longer marked as stale. |
See related: #55359 |
While |
ZD-5548. |
Hi, this issue is becoming a bit of an ongoing joke now. Network manager has been around for years and is the recommended way to manage networking on EL base Linux distributions. I can see a fully working network manager integration has been requested for years and this issue has even been given a P1 label in May 2021 and since then all the public activity on it has been pushing it further into the future with no rationale as to why such a fundamental server component has still not been implemented. I have most of a network state working with network manager after finding a number of undocumented parameters in the Python code however, the final piece to this puzzle is how to trigger the reload. The obvious workaround to the state/module not doing the reload is to do the reload using cmd.run and have a onchanges requisite trigger this however, I try to use cmd.run as a last resort. Can anyone give an update on what is happening with this and whether a working network manager integration is likely to be released any time soon? Regards, |
I made a PR to check for EL8 and call for a NetworkManager restart instead of network. It has been merged, but unknown when this will be released, of course. I currently have it in salt://_modules/rh_ip.py and sync it as a custom to override the default. #61658 |
I've installed version 3005, the error is indeed gone. But Salt still uses network-scripts, which is deprecated since RHEL8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.5_release_notes/deprecated_functionality#deprecated-functionality_networking So it's still not really a fix, adding routes on RHEL8 is still a challenge. For now I'll look for an ad-hoc command with nmcli to add routes. Not great, not terrible. |
This issue also affects RHEL9, and RHEL derivatives such as AlmaLinux and Rocky Linux. You could work around the unmaintained |
network.txt
Description of Issue
With latest salstack 2019 i can't find a way to manage networking on CentOS 8 with state.network, maybe because of CentOS8 rely on networkmanager
Setup
sls file attached, but with centos6 and centos7 it work without any issue.
Steps to Reproduce Issue
try to configure networking on CentOS8, no ifcfg-ifname is generated, and network dosen't work after reboot
Versions Report
Salt Version:
Salt: 2019.2.1
Dependency Versions:
cffi: 1.11.5
cherrypy: unknown
dateutil: 2.6.1
docker-py: Not Installed
gitdb: 2.0.3
gitpython: 2.1.11
ioflo: Not Installed
Jinja2: 2.10.1
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: 0.33.0
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.6.1
mysql-python: Not Installed
pycparser: 2.14
pycrypto: Not Installed
pycryptodome: Not Installed
pygit2: Not Installed
Python: 3.6.8 (default, Jul 1 2019, 16:43:04)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 17.0.0
RAET: Not Installed
smmap: 2.0.3
timelib: Not Installed
Tornado: 4.5.2
ZMQ: 4.3.1
System Versions:
dist: centos 8.0.1905 Core
locale: UTF-8
machine: x86_64
release: 4.18.0-80.7.1.el8_0.x86_64
system: Linux
version: CentOS Linux 8.0.1905 Core
The text was updated successfully, but these errors were encountered: