Project

General

Profile

Bug #6883

Activation key content views and environments applied in "wrong" order

Added by Thomas McKay about 6 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103345
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.

Associated revisions

Revision 88c01eaa (diff)
Added by Thomas McKay about 6 years ago

fixes #6883 - reverse order of activation keys

Revision 78c3c6c5
Added by Thomas McKay about 6 years ago

Merge pull request #4526 from thomasmckay/6883-actkey-order

fixes #6883 - reverse order of activation keys

History

#1 Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 54
  • Pull request https://github.com/Katello/katello/pull/4526 added
  • Pull request deleted ()

#2 Updated by Thomas McKay about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Eric Helms about 6 years ago

  • Category set to 81
  • Triaged changed from No to Yes

#4 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 13

Also available in: Atom PDF