Bug 1399428

Summary:

Anaconda Environment Groups not available to Content View that is applying a filter

Product:

Red Hat Satellite

Reporter:

Paul Dudley <pdudley>

Component:

Content Views

Assignee:

satellite6-bugs <satellite6-bugs>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

6.2.4

CC:

bbuckingham, bkearney, chsimon, inecas, jalviso, jappleii, mhrivnak, pdudley, suarora, yundtj

Target Milestone:

Unspecified

Keywords:

Reopened, Triaged

Target Release:

Unused

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2019-11-04 14:02:49 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Attachments:

Description	Flags
yum grouplist without a CV filter	none
yum grouplist with a CV filter	none

Description Paul Dudley 2016-11-29 04:25:55 UTC

Description of problem:
A system behind a content view that is filtering any content no longer has access to Anaconda Environment groups.

A system under Content View with no filter:
# yum grouplist
...
Available Environment Groups:
   Minimal Install
   Infrastructure Server
   File and Print Server
   MATE Desktop
   Basic Web Server
   Virtualization Host
   Server with GUI
...

The same system  behind the same Content View, only with the package 'Watchdog' filtered out.
**Anaconda Environment Groups are not listed and cannot be used**
# yum groupinstall 'Server with GUI'
...
Warning: group Server with GUI does not exist.
...

How reproducible:
Easily reproduced - This seem to work regardless of which package you filer. At the moment, only an exclude filter was tested.

Steps to Reproduce:
1. # yum grouplist on system that is under a Content View that does not have a filter.
2. Apply filter to Content View
3. # yum grouplist again with the filtered view

Comment 3 Brad Buckingham 2017-05-11 14:51:38 UTC

On Satellite 6.2.9, I am not able to reproduce this behavior.

Scenario 1:
- create a content view with RHEL 7 Server repository (no filters)
- publish the CV
- register a client to the CV
- yum grouplist <- shows list of package groups

Scenario 2:
- create a content view with RHEL 7 Server repository
- add an errata by date filter to exclude any errata created after May 11, 2016
- publish a CV
- register a client to the CV
- yum grouplist <- show list of package groups

Am I missing something?  

I will attach next output of the 2 grouplist outputs.

Comment 4 Brad Buckingham 2017-05-11 14:52:39 UTC

Created attachment 1277915 [details]
yum grouplist without a CV filter

Comment 5 Brad Buckingham 2017-05-11 14:53:08 UTC

Created attachment 1277916 [details]
yum grouplist with a CV filter

Comment 6 Paul Dudley 2017-05-11 15:59:50 UTC

Hey, Brad. Thanks for taking a look at this.

It looks like your second attachment would confirm the initial example - that the client can't # yum groupinstall 'Server with GUI' because the Environment Group disappeared.

All of the normal groups are fine, it seems, but what's happening to the environment groups?

Thanks
Paul

Comment 10 Bryan Kearney 2018-09-04 18:03:26 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 12 Bryan Kearney 2019-11-04 14:02:49 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.