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.
DescriptionDouglas Mendizábal
2020-09-03 20:54:04 UTC
Description of problem:
OpenStack SOS reports currently do not include Barbican service logs for deployments that include Barbican.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Generate SOS report in an OpenStack enviroment that includes the optional Barbican key manager service.
Actual results:
SOS report does not include /var/log/containers/barbican/*
Expected results:
Barbican service logs in /var/log/containers/barbican/*.log are included when generating an SOS report for an OpenStack environment that includes Barbican.
Additional info:
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1850534#c3 ? Just still having the question from #c9 : is it sufficient to get the Barbican logs only when running sosreport --all-logs? Or do you request to collect the logs by default?
Comment 2Douglas Mendizábal
2020-09-22 14:16:51 UTC
Given that Barbican is an optional component, I think it makes sense to only include them when running `sosreport --all-logs`.
(In reply to Douglas Mendizábal from comment #2)
> Given that Barbican is an optional component, I think it makes sense to only
> include them when running `sosreport --all-logs`.
As my understanding from https://bugzilla.redhat.com/show_bug.cgi?id=1850534#c8 is, Barbican logs are collected via --all-logs, which is seemed as sufficient.
Closing as not a bug. Let it reopen if the logs should be collected by default.