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 problem:
I did use sosreport on internal testday to gather information from attendees' systems. I did however missed following data:
>network commands
* iptables-save
* ip6tables-save
* ebtables-save
these commands outputs clear rule data without formatting or changes. also, ebtables are not save altogether anyhow in current 7.3 version
>firewalld:
* /var/log/firewalld
this is a file that gets created if user adds --debug flag to firewalld sysconfig
Version-Release number of selected component (if applicable):
sos-3.4-2.el7.noarch
How reproducible:
always
Steps to Reproduce:
sosreport -o firewalld,networking,general
Actual results:
missing data from description above
Expected results:
Additional info:
firewalld log could be missing
RHEL7.4 devel phase finished a month ago, rescheduling to 7.5.
I guess the [ip|ip6|eb]tables-save are required since:
- "iptables -L" output has running config not the saved one
- /etc/sysconfig/iptables-config lacks firewalld-stored info (contrary to RHEL6 where the rules were appended there)
/var/log/firewalld makes sense to collect, sure.
The *tables-save commands write the configuration out from the live data (iow the information is equal to -L). The difference is that the lines are in iptables command format to re-create the table: "-A <chain> ... -j <target>"
We do currently collect this, but only for non-default netns namespaces.
It's easy enough to add if it's really required but excepting the formatting differences this information should already be in a default report.
The firewalld debug logs should be added.
sos currently seems to only collect information about the filter, nat and mangle tables for IPv4 and IPv6. This needs to be extended by using the table information from /proc/net/ip_tables_names for IPv4 and /proc/net/ip6_tables_names for IPv6.
Using the -save commands all rules in all used tables will be added to the report. This information can be used easily for tests without the need to manually rebuild the rule set from the list output.
/var/log/firewalld is to be collected, together with
ip[|6]tables -t <any_table_from_the_/proc/net_file>
The -save commands are rather about collecting same data but in different format - we try to avoid gathering same data multiple times just in different format.
Rather there should be a script (or a tool for sosreport to "add" more such outputs, like for https://bugzilla.redhat.com/show_bug.cgi?id=1483926) that converts the data collected by sos to another required format.
(if you feel upstream could accept also collecting the -save cmds outputs, please open upstream issue in https://github.com/sosreport/sos/issues to discuss it there)
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, 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-2018:0963