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 1853700 - condition too strict in pci plugin /proc/bus/pci/00 existence
Summary: condition too strict in pci plugin /proc/bus/pci/00 existence
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sos
Version: 8.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.3
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On:
Blocks: 1842946 1853701
TreeView+ depends on / blocked
 
Reported: 2020-07-03 15:01 UTC by Miroslav Hradílek
Modified: 2020-11-04 02:00 UTC (History)
10 users (show)

Fixed In Version: sos-3.9.1-5.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1853701 (view as bug list)
Environment:
Last Closed: 2020-11-04 01:58:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:4534 0 None None None 2020-11-04 01:58:38 UTC

Description Miroslav Hradílek 2020-07-03 15:01:14 UTC
Description of problem:

Commit
https://github.com/sosreport/sos/commit/1b70c61d882036e72449e0fca8dd11cb7eb72bcb

causes that lspci commands are not collected on machines without
/proc/bus/pci/00

I'm no PCI expert but it seams that there can still be useful information on machines with different directory structure under /proc/bus/pci/.

There was bug 238778 requesting the commands to be collected and preventing that might constitute a regression in this case.

Version-Release number of selected component (if applicable):
sos-3.9.1-4.el8.noarch (unreleased)

How reproducible:
100% on machine without /proc/bus/pci/00

Steps to Reproduce:
1. sosreport -o pci

Actual results:
Missing "lspci -nnvv" and "lspci -tv".

Expected results:
Collected "lspci -nnvv" and "lspci -tv".

Additional info:
# arch
aarch64

# tree  /proc/bus/pci
/proc/bus/pci
├── 0000:00
│   ├── 00.0
│   ├── 01.0
│   ├── 01.1
│   ├── 01.2
│   ├── 01.3
│   ├── 01.4
│   └── 01.5
├── 0000:01
│   └── 00.0
├── 0000:02
│   └── 00.0
├── 0000:03
│   └── 00.0
├── 0000:04
│   └── 00.0
├── 0000:05
│   └── 00.0
└── devices

Comment 1 Jake Hunsaker 2020-07-03 16:31:21 UTC
The fix has been merged into upstream master:

https://github.com/sosreport/sos/commit/1c87810faf65fa2c6165d917dd3cc51b3c90a969

Comment 2 Pavel Moravec 2020-07-03 18:24:49 UTC
This would be a regression if not fixed in 8.3, hence requesting an exception to 8.3.0.

Thanks for spotting it and fixing in upstream.

Comment 18 errata-xmlrpc 2020-11-04 01:58:15 UTC
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 (sos 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:4534


Note You need to log in before you can comment on or make changes to this bug.