Bug 1103345

Summary: Activation key content views and environments applied in "wrong" order
Product: Red Hat Satellite Reporter: Erik M Jacobs <ejacobs>
Component: Subscription ManagementAssignee: Tom McKay <tomckay>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bbuckingham, jmontleo, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6883
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-11 12:24:47 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:

Description Erik M Jacobs 2014-05-30 19:25:31 UTC 
Description of problem:
When a Host Group applies a list of activation keys:

SA2-SOE,Wordpress

The first activation key in the list determines the content view and the environment for the resulting host. The expectation in a list of this nature is that the last key in the list determines the CV and Env for the resultant host.

My reasoning is as follows:
Most people will stack keys in order from the least complex (base OS, simple add-ons) to the most complex (third-party software and its requirements). If the base OS key is used first, as most people would tend to use it, the resulting host will always get the CV/Env of the base key, and ignore the others.

Version-Release number of selected component (if applicable):
foreman-1.6.0.13-1.el6sat.noarch
foreman-compute-1.6.0.13-1.el6sat.noarch
foreman-gce-1.6.0.13-1.el6sat.noarch
foreman-libvirt-1.6.0.13-1.el6sat.noarch
foreman-ovirt-1.6.0.13-1.el6sat.noarch
foreman-postgresql-1.6.0.13-1.el6sat.noarch
foreman-proxy-1.6.0.6-1.el6sat.noarch
foreman-vmware-1.6.0.13-1.el6sat.noarch
katello-1.5.0-25.el6sat.noarch
katello-ca-1.0-1.noarch
katello-certs-tools-1.5.5-1.el6sat.noarch
katello-installer-0.0.44-1.el6sat.noarch
pulp-katello-plugins-0.3-1.el6sat.noarch
ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch
ruby193-rubygem-foreman_discovery-1.3.0-0.1.rc2.el6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.4-1.el6sat.noarch
ruby193-rubygem-foreman-tasks-0.5.7-2.el6sat.noarch
ruby193-rubygem-katello-1.5.0-51.el6sat.noarch
rubygem-hammer_cli_foreman-0.1.1-5.el6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.el6sat.noarch
rubygem-hammer_cli_katello-0.0.4-4.el6sat.noarch

While this is a bit of nit-picking, regardless of whether we "fix" this or not, it must be clearly documented (in the UI) which activation key will determine the CV/Env if multiples are used.
Comment 1 RHEL Program Management 2014-05-30 19:27:15 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Tom McKay 2014-08-01 11:58:20 UTC 
Created redmine issue http://projects.theforeman.org/issues/6883 from this bug
Comment 4 Bryan Kearney 2014-08-04 22:02:33 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/6883 has been closed
-------------
Thomas McKay
Applied in changeset commit:katello|88c01eaa8db9707a2a166f3da56d299f2f9d47c0.
Comment 7 Bryan Kearney 2014-09-11 12:24:47 UTC 
This was delivered with Satellite 6.0 which was released on 10 September 2014.