The native types should all autorequire the firewalld service #224
Comments
|
Is #197 (very recently merged) relevant? |
|
@alexjfisher Partially. It doesn't actually solve the entire issue which is getting the native types to self-order properly. Basically anything that runs |
|
aren't Autorquires in types kinda like, friendly suggestions? |
|
@igalic Yep, if it exists, use it, if not, don't. But it's a real requires, if it fails, the rest of the chain will fail. However, this is exactly what we want. |
trevor-vaughan
added a commit
to trevor-vaughan/pupmod-voxpupuli-firewalld
that referenced
this issue
Oct 18, 2019
* Added an autorequire for each native type that uses firewall-cmd. This is due to what appears to be the requirement that any firewall-cmd activities occur after the service has been started the first time. Running commands prior to the service start can result in malformed configurations being applied to the system which silently break the firewalld service. * Tested against simp/iptables 6.4.0 Closes voxpupuli#224
trevor-vaughan
added a commit
to trevor-vaughan/pupmod-voxpupuli-firewalld
that referenced
this issue
Oct 18, 2019
* Added an autorequire for each native type that uses firewall-cmd. This is due to what appears to be the requirement that any firewall-cmd activities occur after the service has been started the first time. Running commands prior to the service start can result in malformed configurations being applied to the system which silently break the firewalld service. * Tested against simp/iptables 6.4.0 Closes voxpupuli#224
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per the documentation, if the
firewalldservice is not running, then various commands may appear to work but, in reality, do not.I ran across this with
firewalld_ipsetrecently and it could easily be alleviated by adding a simple autorequires to the native types.The text was updated successfully, but these errors were encountered: