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.
Bug 1720474 - jna package missing in RHEL 8
Summary: jna package missing in RHEL 8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: jna
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.0
Assignee: Honza Horak
QA Contact: Vaclav Danek
URL:
Whiteboard:
Depends On: 1680805
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-14 06:23 UTC by Hynek Mlnarik
Modified: 2020-11-14 06:45 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:25:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KEYCLOAK-10363 0 Critical Open Installation from RHEL 8 rpms - unable to install jna 2019-10-30 18:51:40 UTC
Red Hat Product Errata RHBA-2019:3492 0 None None None 2019-11-05 21:25:03 UTC

Description Hynek Mlnarik 2019-06-14 06:23:14 UTC
Description of problem:

jna package is not available in RHEL 8 while it was available in RHEL 6/7. jna is needed for RHSSO integration with SSSD. This causes RH-SSO packages cannot be installed on RHEL 8.


Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
1. subscription-manager repos --enable=jb-eap-7.1-for-rhel-7-server-rpms --enable=rh-sso-7.2-for-rhel-7-server-rpms
2. dnf groupinstall rh-sso7

Actual results:
Installation fails with

Error: 
 Problem: cannot install the best candidate for the job
  - nothing provides jna needed by rh-sso7-keycloak-server-4.8.8-1.Final_redhat_00001.1.el8sso.noarch


Expected results:
Installation successful

Additional info:
jna package is available in codeready-builder-for-rhel-8-x86_64-rpms repository. Enabling this repository in addition to jb-eap and rh-sso ones alleviates the problem. However, the package is not supported per https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/package_manifest/chap-codereadybuilder-repository, so this is not viable option for RH-SSO.

Comment 1 Jakub Jančo 2019-06-14 08:30:16 UTC
I also mentioned, that JNA is required while connecting mariadb java driver to database over unix sockets. What do you think Honza?

Comment 16 errata-xmlrpc 2019-11-05 21:25:02 UTC
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://access.redhat.com/errata/RHBA-2019:3492


Note You need to log in before you can comment on or make changes to this bug.