Bug 1389323 - Rebuild of redhat-release-server to a higher version than that of RHEL-7.3
Summary: Rebuild of redhat-release-server to a higher version than that of RHEL-7.3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: releng
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.1.3 Async
Assignee: Sreenath G
QA Contact: Byreddy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 12:53 UTC by Sreenath G
Modified: 2016-11-15 09:33 UTC (History)
9 users (show)

Fixed In Version: redhat-release-server-7.3-8.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 09:33:56 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sreenath G 2016-10-27 12:53:13 UTC 
Description of problem:
redhat-release-server-7.3-6.el7rhgs in RHGS-3.1-z-RHEL-7.3 will get updated by the RHEL one (redhat-release-server-7.3-7.el7), which need to be avoided.


Version-Release number of selected component (if applicable):
7.3-6.el7rhgs

How reproducible:
while performing "yum update"

Steps to Reproduce:
1.
2.
3.

Actual results:
redhat-release-server-7.3-6.el7rhgs < redhat-release-server-7.3-7.el7

Expected results:
redhat-release-server version should be higher for RHGS than RHEL-7.3

Additional info:
Comment 4 Sreenath G 2016-10-28 08:57:34 UTC 
redhat-release-server-7.3-8.el7rhgs[1] built and attached to ET#25303

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=520568
Comment 5 Byreddy 2016-10-28 09:17:07 UTC 
i am seeing higher version of rhgs package redhat-release-server compared to RHEL7.3  in the erratum and while updating rhgs nodes, redhat-release-server-7.3-8.el7rhgs package is picked for the update.


Moving to verified state.
Comment 6 Rejy M Cyriac 2016-11-15 09:33:56 UTC 
Shipped Live:

https://rhn.redhat.com/errata/RHEA-2016-2123.html
Note You need to log in before you can comment on or make changes to this bug.