Bug 503164 - The fcoe-utils package is missing libhbalinux as a dependency
The fcoe-utils package is missing libhbalinux as a dependency
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: fcoe-utils (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Jan Zeleny
Depends On:
  Show dependency treegraph
Reported: 2009-05-29 07:23 EDT by Jan Zeleny
Modified: 2009-09-02 06:02 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 497605
Last Closed: 2009-09-02 06:02:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Zeleny 2009-05-29 07:23:16 EDT
Description of problem:
fcoe-utils should depend on libhbalinux and libhbalinux should depend on
libhbaapi, however, fcoe-utils depends on libhbaapi but neither depends on
libhbalinux so libhbalinux must be installed as a separate step.

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

Steps to Reproduce:
1. # yum -y fcoe-utils
2. Note that libhbalinux does not get installed.

Actual results:
libhbaapi and fcoe-utils get installed but libhbaapi does not.

Expected results:
libhbalinux should get installed as a dependency of fcoe-utils and libhbaapi
should be installed as a dependency of libhbaapi
Comment 1 RHEL Product and Program Management 2009-05-29 07:29:40 EDT
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 8 errata-xmlrpc 2009-09-02 06:02:21 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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