Bug 1300385 - Rebase glusterfs client rpms to the latest in RHEL 7.3
Summary: Rebase glusterfs client rpms to the latest in RHEL 7.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glusterfs
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Milind Changire
QA Contact: Anoop
URL:
Whiteboard:
Depends On:
Blocks: 1298558 1313485
TreeView+ depends on / blocked
 
Reported: 2016-01-20 15:56 UTC by Vivek Agarwal
Modified: 2016-11-04 07:33 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.7.9-12.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 07:33:58 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1450 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2016-11-03 14:09:55 UTC

Description Vivek Agarwal 2016-01-20 15:56:02 UTC
Description of problem:

Rebase glusterfs client rpms to the latest in RHEL 7.3

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 10 Milind Changire 2016-08-24 10:09:32 UTC
Request to tag build glusterfs-3.7.9-12.el7 for RHEL 7.3

Comment 11 Byreddy 2016-08-31 03:46:43 UTC
Changed the Fixed in Version to glusterfs-3.7.9-12.el7

Comment 12 Byreddy 2016-09-29 09:56:49 UTC
i am able to update to glusterfs-3.7.9-12.el7  using the rhel base channel in the stage env.

Moving bug to verified state.

Comment 14 errata-xmlrpc 2016-11-04 07:33:58 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://rhn.redhat.com/errata/RHBA-2016-1450.html


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