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 472708[details]
Example spec file to demonstrate the problem
Description of problem:
In RHEL 6 the exit status of rpm -V doesn't indicate failures of the verifyscript specified in the spec file. Furthermore the verify script is executed twice.
Version-Release number of selected component (if applicable):
# rpm --version
RPM version 4.8.0
How reproducible:
Steps to Reproduce:
1. Build RPM package with attached example spec file
2. Run "rpm -V verifytest-1.0-1.0"
Actual results:
rpm outputs the following (indicating that the verify script is run twice)
In Verify Script
warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1
In Verify Script
warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1
echo $? after the command completes reports 0 (success).
Expected results (as observed on RHEL 5.5):
rpm outputs the following (indicating that the verify script is run once):
In Verify Script
warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1
echo $? after the command completes reports 2 (failure).
Additional info:
A simple example spec file to demonstrate the issue is attached.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0739.html
Created attachment 472708 [details] Example spec file to demonstrate the problem Description of problem: In RHEL 6 the exit status of rpm -V doesn't indicate failures of the verifyscript specified in the spec file. Furthermore the verify script is executed twice. Version-Release number of selected component (if applicable): # rpm --version RPM version 4.8.0 How reproducible: Steps to Reproduce: 1. Build RPM package with attached example spec file 2. Run "rpm -V verifytest-1.0-1.0" Actual results: rpm outputs the following (indicating that the verify script is run twice) In Verify Script warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1 In Verify Script warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1 echo $? after the command completes reports 0 (success). Expected results (as observed on RHEL 5.5): rpm outputs the following (indicating that the verify script is run once): In Verify Script warning: %verify(verifytest-1.0-1.0.x86_64) scriptlet failed, exit status 1 echo $? after the command completes reports 2 (failure). Additional info: A simple example spec file to demonstrate the issue is attached.