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.

From rpmdiff "Brewtap results":

Certain files are expected to have corresponding man pages; as of 2012-11-28 the rule is that: (a) any executable regular file foo in /bin /sbin /usr/sbin or /etc/init.d; or (b) any file marked as %config in the specfile; should have a corresponding man page in /usr/share/man.

Hint: if you see this warning on a file in /etc, reassess whether you should be marking the file as %config: if it's not meant to be touched by a sysadmin, it probably shouldn't be %config.
 	No man page for /etc/ld.so.conf.d/libiscsi-i386.conf
 	No man page for /etc/ld.so.conf.d/libiscsi-x86_64.conf
 	etc.

Committed in libiscsi-1.9.0-3.el7

Hi Paolo,

I have no idea about reproduce/verify this bug , could you help update some suggestions here.

Thanks,
Mazhang.

https://rpmdiff.lab.eng.brq.redhat.com/run/47008/99/ is the latest rpmdiff run I found, you can see that the bug is not there.

(In reply to Paolo Bonzini from comment #5)
> https://rpmdiff.lab.eng.brq.redhat.com/run/47008/99/ is the latest rpmdiff
> run I found, you can see that the bug is not there.

1. Seems the link you pasted is qemu-kvm rpmdiff. 
2. This bug fixed in libiscsi-1.9.0-3.el7, so I run a group of rpmdiff tests for libiscsi-1.9.0-6.el7 compared to libiscsi-1.9.0-2.el7, analysis of libiscsi-1.9.0-6.el7 and analysis of libiscsi-1.9.0-3.el7.
Result:
https://rpmdiff.lab.eng.brq.redhat.com/run/47009/
https://rpmdiff.lab.eng.brq.redhat.com/run/47010/
https://rpmdiff.lab.eng.brq.redhat.com/run/47011/

All result is "Needs inspection", and seems they are no Brewtap results.

"Light green" means passed.  You can add "99/" to the URL manually, BrewTap now passes.

Also,

https://rpmdiff.lab.eng.brq.redhat.com/run/47009/21/

shows that the bug has been fixed.

Run a group of rpmdiff tests for libiscsi-1.9.0-6.el7 compared to libiscsi-1.9.0-2.el7, analysis of libiscsi-1.9.0-6.el7 and analysis of libiscsi-1.9.0-3.el7.

Result:
https://rpmdiff.lab.eng.brq.redhat.com/run/47009/99
https://rpmdiff.lab.eng.brq.redhat.com/run/47010/99
https://rpmdiff.lab.eng.brq.redhat.com/run/47011/99

Brewtap results passed, so this bug has been fixed.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.