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.
Created attachment 1332888[details]
sos file for example
Description of problem:
sos-report do not collect OVN logs that located under
/var/log/openstack/
[root@controller-1 ~]# ll /var/log/openvswitch/
total 1780
-rw-r--r--. 1 root root 98898 Oct 1 09:57 ovn-controller.log
-rw-r--r--. 1 root root 811 Oct 1 09:09 ovn-northd.log
-rw-r--r--. 1 root root 359 Oct 1 08:47 ovsdb-server.log
-rw-r--r--. 1 root root 686715 Oct 1 10:50 ovsdb-server-nb.log
-rw-r--r--. 1 root root 684991 Oct 1 10:50 ovsdb-server-sb.log
-rw-r--r--. 1 root root 4042 Oct 1 09:57 ovs-vswitchd.log
Version-Release number of selected component (if applicable):
12 -p 2017-09-28.1
[root@controller-1 ~]# rpm -qa |grep sos
sos-3.4-6.el7.noarch
[root@controller-1 ~]# rpm -qa |grep ovn
openvswitch-ovn-common-2.7.2-4.git20170719.el7fdp.x86_64
puppet-ovn-11.3.1-0.20170825135756.c03c3ed.el7ost.noarch
openvswitch-ovn-central-2.7.2-4.git20170719.el7fdp.x86_64
openvswitch-ovn-host-2.7.2-4.git20170719.el7fdp.x86_64
python-networking-ovn-3.0.1-0.20170906223255.c663db6.el7ost.noarch
How reproducible:
always
Steps to Reproduce:
Steps to Reproduce:
1. Deploy Director HA Pike with OVN
2. create netwrok& subnet
3. check the log under /var/log/openvswitch/
4. run sos report and check the file that created.
Actual results:
ovn logs do not collect by sos
Expected results:
all logs should collect by sos report
Additional info:
Thanks for report. Few questions before I submit upstream PR for this:
- (just to (silently) confirm): we should collect those log when 'openvswitch' or 'openvswitch-dpdk' packages are installed, I expect.
- whole /var/log/openvswitch/ directory should be collected? Or e.g. just /var/log/openvswitch/*log or some specific set of logfiles?
- some size limit constrains? (default is 10MB of newest logs, until --all-logs option is used, usually it is sufficient)
- could there be some secret data (passwords or so) that we should obfuscate? (usually not, but it could happen)
(In reply to Pavel Moravec from comment #3)
> Thanks for report. Few questions before I submit upstream PR for this:
>
> - (just to (silently) confirm): we should collect those log when
> 'openvswitch' or 'openvswitch-dpdk' packages are installed, I expect.
>
> - whole /var/log/openvswitch/ directory should be collected? Or e.g. just
> /var/log/openvswitch/*log or some specific set of logfiles?
I expect to get OVN logs under sos report.
> - some size limit constraints? (default is 10MB of newest logs, until
> --all-logs option is used, usually, it is sufficient)
cant answer about it.
> - could there be some secret data (passwords or so) that we should
> obfuscate? (usually not, but it could happen)
I don't think so but it better to ask OVN developers.
Maybe Numan can answer that...
(In reply to Eran Kuris from comment #4)
> (In reply to Pavel Moravec from comment #3)
> > Thanks for report. Few questions before I submit upstream PR for this:
> >
> > - (just to (silently) confirm): we should collect those log when
> > 'openvswitch' or 'openvswitch-dpdk' packages are installed, I expect.
> >
> > - whole /var/log/openvswitch/ directory should be collected? Or e.g. just
> > /var/log/openvswitch/*log or some specific set of logfiles?
> I expect to get OVN logs under sos report.
I would prefer whole directory. All the OVN logs end with *.log though.
>
> > - some size limit constraints? (default is 10MB of newest logs, until
> > --all-logs option is used, usually, it is sufficient)
> cant answer about it.
That seems fine.
>
> > - could there be some secret data (passwords or so) that we should
> > obfuscate? (usually not, but it could happen)
> I don't think so but it better to ask OVN developers.
> Maybe Numan can answer that...
I don't think there is any secret data in the logs.
> I would prefer whole directory. All the OVN logs end with *.log though.
Log collection needs to obey the standard --log-size=N and --all-logs switches; if those are given and log size limits are disabled then the whole directory will be collected.
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
Created attachment 1332888 [details] sos file for example Description of problem: sos-report do not collect OVN logs that located under /var/log/openstack/ [root@controller-1 ~]# ll /var/log/openvswitch/ total 1780 -rw-r--r--. 1 root root 98898 Oct 1 09:57 ovn-controller.log -rw-r--r--. 1 root root 811 Oct 1 09:09 ovn-northd.log -rw-r--r--. 1 root root 359 Oct 1 08:47 ovsdb-server.log -rw-r--r--. 1 root root 686715 Oct 1 10:50 ovsdb-server-nb.log -rw-r--r--. 1 root root 684991 Oct 1 10:50 ovsdb-server-sb.log -rw-r--r--. 1 root root 4042 Oct 1 09:57 ovs-vswitchd.log Version-Release number of selected component (if applicable): 12 -p 2017-09-28.1 [root@controller-1 ~]# rpm -qa |grep sos sos-3.4-6.el7.noarch [root@controller-1 ~]# rpm -qa |grep ovn openvswitch-ovn-common-2.7.2-4.git20170719.el7fdp.x86_64 puppet-ovn-11.3.1-0.20170825135756.c03c3ed.el7ost.noarch openvswitch-ovn-central-2.7.2-4.git20170719.el7fdp.x86_64 openvswitch-ovn-host-2.7.2-4.git20170719.el7fdp.x86_64 python-networking-ovn-3.0.1-0.20170906223255.c663db6.el7ost.noarch How reproducible: always Steps to Reproduce: Steps to Reproduce: 1. Deploy Director HA Pike with OVN 2. create netwrok& subnet 3. check the log under /var/log/openvswitch/ 4. run sos report and check the file that created. Actual results: ovn logs do not collect by sos Expected results: all logs should collect by sos report Additional info: