Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.The `logging` RHEL System Role now supports port access and generation of the certificates
With this enhancement, you can use the logging role to manage ports access and generate certificates with new role variables. If you set the new role variables `logging_manage_firewall` and `logging_manage_selinux` to `true`, the roles manage port access. The new role variable for generating certificates is `logging_certificates`. The type and usage are the same as the `certificate` role `certificate_requests`. You can now automate these operations directly by using the `logging` role.
Description of problem:
The logging role can use the firewall role and the selinux role to manage port access.
The logging role can use the certificate role to generate certificates.
New variables
- `logging_manage_firewall`: If set to `true` and ports are found in the logging role
parameters, configure the firewall for the ports using the firewall role.
If set to `false`, the `logging role` does not manage the firewall.
Default to `false`.
NOTE: `logging_manage_firewall` is limited to *adding* ports.
It cannot be used for *removing* ports.
If you want to remove ports, you will need to use the firewall system
role directly.
- `logging_manage_selinux`: If set to `true` and ports are found in the logging role
parameters, configure the selinux for the ports using the selinux role.
If set to `false`, the `logging role` does not manage the selinux.
Default to `false`.
NOTE: `logging_manage_selinux` is limited to *adding* policy.
It cannot be used for *removing* policy.
If you want to remove policy, you will need to use the selinux system
role directly.
- `logging_certificates`: This is a `list` of `dict` in the same format as used
by the `fedora.linux_system_roles.certificate` role. Specify this variable if
you want the certificate role to generate the certificates for the logging system
configured by the logging role. With this example, `self-signed` certificate
`logging_cert.crt` is generated in `/etc/pki/tls/certs`.
Default to `[]`.
```yaml
logging_certificates:
- name: logging_cert
dns: ['localhost', 'www.example.com']
ca: self-sign
```
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2023:2246
Description of problem: The logging role can use the firewall role and the selinux role to manage port access. The logging role can use the certificate role to generate certificates. New variables - `logging_manage_firewall`: If set to `true` and ports are found in the logging role parameters, configure the firewall for the ports using the firewall role. If set to `false`, the `logging role` does not manage the firewall. Default to `false`. NOTE: `logging_manage_firewall` is limited to *adding* ports. It cannot be used for *removing* ports. If you want to remove ports, you will need to use the firewall system role directly. - `logging_manage_selinux`: If set to `true` and ports are found in the logging role parameters, configure the selinux for the ports using the selinux role. If set to `false`, the `logging role` does not manage the selinux. Default to `false`. NOTE: `logging_manage_selinux` is limited to *adding* policy. It cannot be used for *removing* policy. If you want to remove policy, you will need to use the selinux system role directly. - `logging_certificates`: This is a `list` of `dict` in the same format as used by the `fedora.linux_system_roles.certificate` role. Specify this variable if you want the certificate role to generate the certificates for the logging system configured by the logging role. With this example, `self-signed` certificate `logging_cert.crt` is generated in `/etc/pki/tls/certs`. Default to `[]`. ```yaml logging_certificates: - name: logging_cert dns: ['localhost', 'www.example.com'] ca: self-sign ```