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 1840667 - ubi8's yum repository does not provide libaio-devel package to enable aysnc io/io-engines
Summary: ubi8's yum repository does not provide libaio-devel package to enable aysnc i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: distribution
Version: 8.0
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: RHEL Program Management
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-27 12:33 UTC by Lakshmi Ravichandran
Modified: 2024-02-14 20:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-27 17:28:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lakshmi Ravichandran 2020-05-27 12:33:53 UTC
Description of problem:
ubi8's yum repository does not provide libaio-devel package to enable aysnc io/io-engines to be used with disk stressing tools like fio (https://fio.readthedocs.io/en/latest/fio_doc.html). 


Version-Release number of selected component (if applicable):
registry.access.redhat.com/ubi8/ubi:latest

ubi8 provides only "libaio" library, which singly does not help in getting the libaio-engine enabled for aysnc io.

How reproducible:
create a container image based on ubi8 and fio tool:
for e.g:
FROM registry.access.redhat.com/ubi8/ubi:latest

RUN yum -y install gcc make git libaio

RUN git clone git://github.com/axboe/fio.git fio && cd fio/ && ./configure && make && make install


Steps to Reproduce:
1. Run the above example container 
2. Invoke fio command with libaio as ioengine -  for e.g.
fio --name=randwrite --ioengine=libaio --iodepth=1 --rw=randwrite --bs=4k --direct=0 --size=512M --numjobs=2 --group_reporting --time_based --runtime=90 --dir=/test_data
3. watch the command fail

Actual results:
[root@xxx fio]# fio --name=randwrite --ioengine=libaio --iodepth=1 --rw=randwrite --bs=4k --direct=0 --size=512M --numjobs=2 --group_reporting --time_based --runtime=90 --dir=/test_data
fio: engine libaio not loadable
fio: engine libaio not loadable
fio: failed to load engine
fio: file:ioengines.c:89, func=dlopen, error=libaio: cannot open shared object file: No such file or directory

Expected results:
fio command should succeed with libaio engine

Additional info:
libaio-devel package is available yum repository of RHEL 8.0 and fio could run successfully with it.

Comment 1 Josh Boyer 2020-05-27 17:28:54 UTC
Thank you for the request.  Today, UBI is really targeted towards cloud native, application developers working with languages like Java, Node.js, Golang, .Net, Perl, Python, Ruby, and PHP [1]. Currently, this request does not fall within the currently approved use cases for inclusion in UBI. The scope of UBI will likely grow and we will keep this use case in mind.

If you're building an image as a Red Hat partner, you might be able to use the Red Hat Partner Connect program [2] to distribute the content you need.

[1] https://developers.redhat.com/blog/2019/10/09/what-is-red-hat-universal-base-image/
[2] https://developers.redhat.com/blog/2020/02/26/red-hat-simplifies-container-dev-and-redistribution-rhel-packages/

Comment 3 Lucas Theisen 2024-02-14 20:45:26 UTC
This seems like an odd decision. This specific library (libaio-devel) is required for the oracle instant client which is used by ODBC for `.Net` code as well as the `python` `cx_Oracle` client to connect to oracle.  That seems to fit with your statement

> targeted towards cloud native, application developers working with languages like ..., .Net, ..., Python

Do you have a workaround to getting this library?


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