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 1456524 - [Mellanox 7.5 FEAT] opensm: update package
Summary: [Mellanox 7.5 FEAT] opensm: update package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: opensm
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Honggang LI
QA Contact: Mike Stowell
URL:
Whiteboard:
Depends On:
Blocks: 1432225 1442258
TreeView+ depends on / blocked
 
Reported: 2017-05-29 14:04 UTC by Slava Shwartsman
Modified: 2018-04-10 17:51 UTC (History)
11 users (show)

Fixed In Version: opensm-3.3.20-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 17:48:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0954 0 None None None 2018-04-10 17:51:04 UTC

Description Slava Shwartsman 2017-05-29 14:04:40 UTC
1. Feature Overview:
        a) Name of feature:
                Update opensm package
        b) Feature description:
                This feature request is for update the opensm package to include the latest bug fixes and features.

2. Feature Details:
        a) Architectures:
                x86_64, ppc64le, ppc64, aarch64
        b) Bugzilla dependencies:
        c) Drivers or hardware dependencies:
                bash
                glibc
                libibumad
                logrotate
                opensm-libs
        d) Upstream acceptance information:
        e) External links:
        f) Severity (H, M, L):
                High
        g) Feature needed by:
                Partner: Mellanox

3. Business Justification:
        a) why is this feature needed?
        b) What hardware does this enable?
        c) Business impact?
        d) Other business drivers?

4. Primary contact at Red Hat, email, phone (chat):
        Andre Beausoleil abeausol

5. Primary contact at Partner, email. phone (chat):
        Kamal Heib kheib, Slava Shwartsman sshwarts, Noa Spanier noas

Comment 2 Slava Shwartsman 2017-07-02 13:20:34 UTC
Mellanox would like an update for this package to the latest upstream:
3.3.20

Comment 7 errata-xmlrpc 2018-04-10 17:48:59 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/RHEA-2018:0954


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