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.
DescriptionBrian J. Murrell
2023-05-26 19:37:34 UTC
Created attachment 1967164[details]
mock output showing error
Description of problem:
Using mock to build on RHEL7 fails when trying to install java-1.8.0-openjdk-headless-1:1.8.0.372.b07-1.el7_9 in the mock chroot.
Version-Release number of selected component (if applicable):
1.8.0.372.b07-1.el7_9
How reproducible:
100%
This appears to be related to bug#1892224 but that one is closed as resolved and in Fedora. This one is in RHEL 7.9.
Could I please get a status update on this one? We do still need to support EL7 in our software stack.
Comment 4Andrew John Hughes
2023-07-26 13:33:36 UTC
Error is:
Running scriptlet: java-1.8.0-openjdk-headless-1:1.8.0.372.b07-1.el7_9. 1/1
error: lua script failed: /var/lib/rpm-state//copy_jdk_configs.lua:39: attempt to index a nil value (global 'arg')
Reassigning to copy-jdk-configs as that's where the copy_jdk_configs.lua script lives.
Comment 5Andrew John Hughes
2023-07-26 13:36:27 UTC
This is a little confusing because, yes, the copy_jdk_configs.lua script in RHEL 7.9 does not have the fix in the referenced Fedora bug #1892224 (https://pagure.io/copy_jdk_configs/pull-request/1#request_diff) but then it also still uses rpm 4.11. The fix was a result of a change in rpm 4.17, apparently. I can't see any obvious changes to the rpm package in 7.9 that would cause this to break now.
Hopefully Jiri can shed more light on this.
Comment 6RHEL Program Management
2023-09-12 23:13:35 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7RHEL Program Management
2023-09-12 23:14:06 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.