Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1323768

Summary: New Host Group form ignores selected Content View and shows all available ActivationKeys
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: Content ManagementAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, rplevka
Target Milestone: UnspecifiedKeywords: PrioBumpQA, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14804
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:08:12 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:
Embargoed:
Attachments:
Description Flags
ActivationKeys
none
Host Group form none

Description Og Maciel 2016-04-04 16:08:46 UTC
Description of problem:

I noticed that when you create a new Host Group, all activationkeys are being displayed, independent of which Content View is selected.

Assuming you have:

* Content View 1
  * ActivationKey 1
* ContentView 2
  * ActivationKey 2

If you select Content View 1 when filing out the new Host Group form, you should only see ActivationKey 1 as your only choice

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

* Satellite 6.2.0 SNAP 6.1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Og Maciel 2016-04-04 16:10:40 UTC
Created attachment 1143387 [details]
ActivationKeys

This screenshot shows that I have 2 screenshots, each associated to the same Lifecycle Environment (DEV) but different (published) Content Views.

Comment 2 Og Maciel 2016-04-04 16:11:51 UTC
Created attachment 1143389 [details]
Host Group form

This screenshot shows that 2 activationkeys are available to my Host Group but only one of them should be listed.

Comment 4 Brad Buckingham 2016-04-21 20:46:38 UTC
WORKAROUND: 

Select from the list of activation keys, one that has the same Lifecycle Environment and Content View as the host group being created.

Comment 5 John Mitsch 2016-04-25 18:58:17 UTC
Created redmine issue http://projects.theforeman.org/issues/14804 from this bug

Comment 6 Bryan Kearney 2016-04-25 20:18:35 UTC
Upstream bug component is Content Management

Comment 7 Bryan Kearney 2016-04-28 16:16:19 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14804 has been closed

Comment 8 Roman Plevka 2016-05-25 10:43:25 UTC
VERIFIED:

on sat6.2.0 Beta (GA12.1)
the activation keys now correctly suggest only the appropriate values.
tested with the same setup as stated in the description.

Comment 9 Bryan Kearney 2016-07-27 11:08:12 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/RHBA-2016:1501