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.

The osci.brew-build.rpminspect.static-analysis test against the latest pki-core build failed:
https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/37807837

Here are some of the error messages:
http://artifacts.osci.redhat.com/testing-farm/085d0694-824d-43d5-bdf9-6be929f40d18/work-rpminspectO5DoPf/rpminspect/execute/data/annocheck/output.txt

Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: stack-clash test because -fstack-clash-protection not enabled (function: _ZN7JNIEnv_9NewObjectEP7_jclassP10_jmethodIDz) 
...
Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: cf-protection test because no protection enabled (function: _ZN7JNIEnv_9NewObjectEP7_jclassP10_jmethodIDz) 
Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: cf-protection test because no protection enabled (function: _ZN6BufferC2EPKhj) 
Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: cf-protection test because no protection enabled (function: _ZN6BufferC1Ej) 
Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: cf-protection test because no protection enabled (function: _ZN6BufferC1Ejh) 
Hardened: /usr/lib64/symkey/libsymkey.so: FAIL: cf-protection test because no protection enabled (function: _ZN6BufferD2Ev) 
...

This issue blocks pki-core gating on RHEL 9 and cannot be waived.

Possibly caused by gating tool issue:
https://mailman-int.corp.redhat.com/archives/rhel-devel/2021-June/msg00640.html

> Yes, this is worrying.  My guess is that it is due to another update
> to annobin, probably for version 9.76, which was built on June 15, but
> again it takes time for a build to make it into the buildroot, so maybe
> this is the cause.

The log shows these messages:

Hardened: Hardened: /usr/lib64/symkey/libsymkey.so: The annobin plugin was built by an older version of the compiler.
Hardened: debug: Annobin plugin was built by gcc 11.0.1 but run on gcc version 11.1.1.
Hardened: debug: If there are WARN or FAIL results that appear to be incorrect, it could be due to this discrepancy.

Since we think that this may be caused by a gating tool issue, and may go away once the tool is fixed, assigning an ITM of 24.

The failure can actually be waived:
https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/37847294

Reassigning to annobin. Please close if this is a duplicate. Thanks!

Fixed in annobin-9.79-1.el9

Actually this is a duplicate of 1978176

*** This bug has been marked as a duplicate of bug 1978176 ***