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.
Descriptionnikhil kshirsagar
2016-03-28 05:01:11 UTC
Description of problem:
[root@legspki01 yum.repos.d]# fcoeadm -i
fcoeadm: libHBAAPI or libhbalinux error
Version-Release number of selected component (if applicable):
libhbalinux-1.0.17-2.el7.x86_64
Additional info:
This seems the same issue as bz 700007. However that says that the issue is fixed in libhbalinux-1.0.10-3.el6 and the customer reports version libhbalinux-1.0.17-2.el7.x86_64
Could this be a regression, or has the fix not gone into RHEL 7?
I am seeing the same issue...why was this closed as NOTABUG?
My software versions:
libhbaapi-.2.9-6.el7.x86_64
libhbalinux-1.0.17-2.el7.x86_64
fcoe-utils-1.0.30-3.git91c0c8c.el7.x86_64
What is going on here?
(In reply to bwoods from comment #4)
> I am seeing the same issue...why was this closed as NOTABUG?
>
> My software versions:
>
> libhbaapi-.2.9-6.el7.x86_64
> libhbalinux-1.0.17-2.el7.x86_64
> fcoe-utils-1.0.30-3.git91c0c8c.el7.x86_64
>
> What is going on here?
It apparently was closed once it was discovered that the original report involved 3rd party driver additions on top of RHEL that we couldn't support.
If that's not true in your case, and you'd be willing to help debug, this could be re-opened.
For instance, if you could provide a copy of /etc/hba.conf from a failed system we could check this against bz 700007
I don't believe that is true in my case. My /etc/hba.conf contains nothing but comments:
#
# This file contains names and references to HBA libraries
#
# Format:
#
# <library name> <library pathname>
#
# The library name should be prepended with the domain of
# the manufacturer or driver author.
#
# 32bit/64bit implementation note:
# If a 32bit implementation tries to load a 64 bit library,
# the load will fail with the result that the 64 bit vendor
# library is ignored.
# Likewise, if a 64bit implementation tries to load a 32 bit library,
# the load will fail with the result that the 32 bit vendor
# library is ignored.
# Set a debug level (depends on compilation switches)
#
# Format:
#
# "debuglevel" <debug level>
#
# 0 is default, 1 show vendor library opens,
# 2 shows function calls, 3 shows callback events
#
# Uncomment the next line to specify a level
#debuglevel 3
I am suffering from this bug as well. Has there been any progress made since bwoods attached the hba.conf? My hda.conf is default as well and fcoeadm -i errors out in the same error message.