Bug 1247520 - Both older "Active Directory Integration" group and the new "RH-Gluster-AD-Integration" groups are present in CDN stage
Summary: Both older "Active Directory Integration" group and the new "RH-Gluster-AD-In...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribution
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Sreenath G
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-28 08:41 UTC by surabhi
Modified: 2019-01-09 03:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-09 03:32:32 UTC
Embargoed:


Attachments (Terms of Use)

Description surabhi 2015-07-28 08:41:04 UTC
Description of problem:

After doing yum update from CDN stage from 3.0.4 to 3.1 , I am seeing both the groups for AD integration available which shouldn't be the case.
The older group shall get updated by the new group.
old group: Active Directory Integration
New group : RH-Gluster-AD-Integration

This worls fine for "Samba(SMB) server" group. The older group is updated by new group "RH-Gluster-Samba".

Also the RHS groups are available in language groups for which another BZ is raised to track.

Available Groups:
   Active Directory Integration


Available Language Groups:
   RH-Gluster-AD-Integration [false]


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

How reproducible:
Always

Steps to Reproduce:
1.Install 3.0.4 , subscribe to CDN Live , add samba cdn repo,yum update.
2.Subscribe to CDN stage , check yum groups 
3.Both the AD groups available.

Actual results:
***************************
Both the Active Directory groups present after update.the old one should get updated with teh new one.


Expected results:
The older group should get updated with the new group as it happens for Samba server group.


Additional info:

Comment 7 Mike McCune 2016-03-28 23:33:48 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 8 Atin Mukherjee 2018-11-08 14:42:52 UTC
Sreenath - Is there any work planned around this? If not, can we close this bug?


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