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 had fresh installed RHEL-7.0-20131222.0 on a ppc64 machine in Beaker.  I ssh'd in and ran `lsvpd`.  The command took long to complete so I hit Ctrl+C to interrupt it.  Segfault.

I was able to reproduce it few times with the fresh machine, but at some point lsvpd only prints "Error reading VPD DB: Failed to fetch requested item." and quits, so I don't get the opportunity to send the Ctrl+C.  (I don't know what this error exactly means and if it can be related to the segfault.)

Version-Release number of selected component (if applicable):
lsvpd-1.7.1-2.el7.ppc64

How reproducible:
n/a

Steps to Reproduce:
1. Install RHEL7 with lsvpd
2. `lsvpd`
   it should take more than 10s
3. Hit Ctrl+C

Actual results:
Segfault

Expected results:
Graceful exit

Additional info:

Created attachment 882241 [details]
abrt problem dir (manually created)

Created attachment 882242 [details]
backtrace

Turns out that if I interrupt vpdupdate itself, it segfaults, which is probably what is happening here.

I have reported it separately, though, as bug 1084065

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

I cannot reproduce the segfault again; the behavior is as Sinny observes above; I'll just add that if the install is fresh, interrupting 'lsvpd' before ever running vpdupdate will bring up "DB corrupted" message, including hint to re-run vpdupdate, which indeed helps.

I agree with Sinny that the problem was in vpdupdate.

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://rhn.redhat.com/errata/RHBA-2016-2340.html