Description of problem: There is no fact/YAML definition available in hosts for their Host collection. This RFE is related to parent RFE below: https://bugzilla.redhat.com/show_bug.cgi?id=1391824 Version-Release number of selected component (if applicable): satellite 6.2 How reproducible: In Satellite 6 (Monitor->Facts), there is no Facts related to host's host collection. In host CLI, #facter does not list any host collection definition. Expected results: Include host's host collection to YAML definition.
This wouldn't propagate into host facts but can be present in ENC output (YAML definition). Once we put it into ENC, user could probably create custom fact definition to get it imported with other facts. Note for implementation - this should be added to https://github.com/Katello/katello/blob/master/app/models/katello/concerns/host_managed_extensions.rb#L53
Created redmine issue http://projects.theforeman.org/issues/17215 from this bug
Hi - Is there any progress on this RFE? Thanks.
Sorry, not yet. Amit, could you check whether the solution described in comment 1 would help the customer? We'd provide the info in ENC answer.
Marek - This bug is related to other bug: Bug 1391824 - [RFE] Add the ability to use host collection as a matcher for smart class parameters. <<--- Marked duplicate of bz1384009 Bug 1384009 - [RFE] using smart variables based on Host Collections Cu want to add host collection as a smart class parameter. Currently there is only four - fqdn,hostgroup,os and domain. We found that host collection is missing in the YAML definition whereas other four parameters are present. Facts is required in each hosts to create a matcher in Smart Class Parameter. Suppose Host collection is added in ENC output (YAML definition) and cu/user is able to create custom fact definition; whether such custom facts can be used to create a matcher in smart class parameter? Meanwhile, I have posted the solution you posted earlier to cu and waiting for response.
Upstream bug assigned to mhulan
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17215 has been resolved.
Hi - Can we have target release for this bug? Is it possible include in satellite next release 6.2.11+ since upstream is resolved. Please let us know more. Thanks
The patch was planned for 6.3 but I think it's trivial to backport it and low risk too. Bryan, what's our policy for upcoming 6.2 and these small RFEs?
Created attachment 1319868 [details] Host collections in params Verified. 6.3.0 snap 13
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