|Summary:||No ability to restrict *_external_variables with search anymore|
|Product:||Red Hat Satellite 6||Reporter:||orabin|
|Component:||Users & Roles||Assignee:||orabin|
|Status:||CLOSED ERRATA||QA Contact:||Renzo Nuccitelli <rnuccite>|
|Version:||6.2.0||CC:||bbuckingham, bkearney, egolov, mhulan, oshtaier, rnuccite, sreber, sthirugn|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-02-21 17:05:05 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description orabin 2016-07-26 08:15:33 UTC
Since Foreman 1.10 it is not possible to restrict Resource="Lookup key" with search anymore. The page to edit says: "Selected resource type does not support granular filtering, therefore you can't configure granularity" In Foreman 1.9 this was working fine.
Comment 1 orabin 2016-07-26 08:15:38 UTC
Created from redmine issue http://projects.theforeman.org/issues/14546
Comment 6 Renzo Nuccitelli 2016-11-11 17:39:43 UTC
Verified for puppet class parameters and Variable lookup key on 6.3 snap 6 version. confirmed bug still on 6.2.4. Worth mentioning that on 6.2.4 there is a resource named "Lookup Key" but on 6.3 only on named "Variable lookup key". So I just want to make sure they are the same and this is only a renaming before changing status.
Comment 7 orabin 2016-11-12 16:58:55 UTC
LookupKey was divided into two resources in 6.3: puppet class lookup key and variable lookup key. Puppet class lookup key is for Smart class parameters and Variable lookup key for Smart variables.
Comment 8 Renzo Nuccitelli 2016-11-14 12:33:59 UTC
I checked both resources mentioned on comment 7 and they have search enabled. So I am changing this bug as verified for version 6.3 snap 6.
Comment 10 Bryan Kearney 2018-02-21 17:05:05 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/RHSA-2018:0336