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.
Bug 1996777 - logging - Update the certificates copy tasks
Summary: logging - Update the certificates copy tasks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 9.0 Beta
Assignee: Rich Megginson
QA Contact: Jakub Haruda
URL:
Whiteboard: role:logging
Depends On: 1994580
Blocks: 1978655
TreeView+ depends on / blocked
 
Reported: 2021-08-23 16:04 UTC by Noriko Hosoi
Modified: 2021-12-07 22:02 UTC (History)
8 users (show)

Fixed In Version: rhel-system-roles-1.8.2-1.el9
Doc Type: Bug Fix
Doc Text:
Cause: In the logging role elasticsearch output, if the path of key/certs source files on the control host are configured in the playbook, even if tls is set to false, they were being copied to the managed hosts. There was a use case that the key/certs file paths are configured and do not exist under the condition of tls is false, and the case failed due to the copy source files did not exist. Fix: It is fixed so that the copying the key/certs is executed only when the tls param is set to true. Consequence: With this fix, the copy failure does not occur if tls is false.
Clone Of: 1994580
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles logging pull 243 0 None None None 2021-08-23 20:27:26 UTC
Red Hat Issue Tracker RHELPLAN-94498 0 None None None 2021-08-23 16:06:54 UTC

Comment 1 Aviv Litman 2021-08-24 10:13:18 UTC 
Verified Flows:
1. tls is false, certs+key defined: task ok, showed the warning (screenshot1, all output is green).
2. tls is false, certs+key empty: task skipped (screenshot2).
3. tls is false, certs+key undefined: task skipped (screenshot2).

I verify also with tls true to make sure the playbook behaves as expected:
4. tls is true, certs+key defined: copy task ok, and check tasks skipped.
5. tls is true, certs+key empty: copy tasks skipped and the playbook failed on the "Check certs - tls is true, but triplets are not given" task.
6. tls is true, certs+key undefined: the playbook failed on the first copy task.

The playbook behaves as expected.
Note You need to log in before you can comment on or make changes to this bug.