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.
Description of fixes of Logging role:
RHELPLAN-45641 - All system roles should use consistent parameter/key names for TLS parameters
- Complying with the consistent tls parameter/key names:
logging_pki_files:
- ca_cert_src: ca cert path on the control host
cert_src: cert path on the control host
key_src: key path on the control host
ca_cert_dest: ca cert path on the managed host
cert_dest: cert paton on the managed host
key_dest: key paton on the managed host
- Updated README.md with better parameter grouping
- In the copy task in tasks/main.yml, which copies the src files to the dest,
added a check whether triplets are given or not.
- Adding a test playbook tests_basics_forwards_cert_missing.yml.
- Put the debug code into a block which is needed by the new test which runs
the second logging role for the recovery from the first failure.
- Complying with the consistent tls parameter/key names in the elasticsearch
output. Replacing ca_cert, cert and key params with ca_cert_dest, cert_dest
and key_dest, respectively.
Design doc:
https://docs.google.com/document/d/1rl1OiNF2LBCGBK3tjgWwPncMBpveyrzFtGhjCkWDWQw/edit#heading=h.iuqo0vi1hvyc
@pcahyna, pr/146 (https://github.com/linux-system-roles/logging/pull/146) was merged some time back.
Is it ok to set devel ack+ (and ask owners to set their +), change the status to POST, and reassign this bug to you?
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-2020:4809
Description of fixes of Logging role: RHELPLAN-45641 - All system roles should use consistent parameter/key names for TLS parameters - Complying with the consistent tls parameter/key names: logging_pki_files: - ca_cert_src: ca cert path on the control host cert_src: cert path on the control host key_src: key path on the control host ca_cert_dest: ca cert path on the managed host cert_dest: cert paton on the managed host key_dest: key paton on the managed host - Updated README.md with better parameter grouping - In the copy task in tasks/main.yml, which copies the src files to the dest, added a check whether triplets are given or not. - Adding a test playbook tests_basics_forwards_cert_missing.yml. - Put the debug code into a block which is needed by the new test which runs the second logging role for the recovery from the first failure. - Complying with the consistent tls parameter/key names in the elasticsearch output. Replacing ca_cert, cert and key params with ca_cert_dest, cert_dest and key_dest, respectively. Design doc: https://docs.google.com/document/d/1rl1OiNF2LBCGBK3tjgWwPncMBpveyrzFtGhjCkWDWQw/edit#heading=h.iuqo0vi1hvyc