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 1650127 - Custom boolean facts with false value are not managed by Satellite.
Summary: Custom boolean facts with false value are not managed by Satellite.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Marek Hulan
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-15 11:56 UTC by Raashika Raghuwanshi
Modified: 2019-10-22 19:51 UTC (History)
3 users (show)

Fixed In Version: foreman-1.21.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:51:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25483 0 'Normal' 'Closed' 'Custom boolean facts with false value are not imported' 2019-12-03 05:40:28 UTC

Description Raashika Raghuwanshi 2018-11-15 11:56:45 UTC
Description of problem:
Custome Boolean Puppet facts with value False are not on the WebUI, Hammer output or with REST API. Only facts with value True are shown/stored.

Version-Release number of selected component (if applicable):
Satellite 6.4
Puppet 5

How reproducible:
Always

Steps to Reproduce:
In /opt/puppetlabs/puppet/cache/lib/facter 

# cat temp.rb
require 'facter'

Facter.add("always_true") do
  confine :kernel => "Linux"
  setcode do
    true
  end
end

Facter.add("always_false") do
  confine :kernel => "Linux"
  setcode do
    false
  end
end

Actual results:
- False value is not displayed
# hammer fact list --search "name=always_true"
----------------------|-------------|------
HOST                  | FACT        | VALUE
----------------------|-------------|------
lvmpig03 | always_true | true
----------------------|-------------|------

Expected results:
- False value should be displayed
# hammer fact list --search "name=always_false"
----------------------|-------------|------
HOST                  | FACT        | VALUE
----------------------|-------------|------
lvmpig03 | always_false | false
lvmpig03 | always_true | true
----------------------|-------------|------

Comment 1 Marek Hulan 2018-11-16 13:32:01 UTC
reproduced, valid bug

Comment 2 Marek Hulan 2018-11-16 13:32:32 UTC
Created redmine issue https://projects.theforeman.org/issues/25483 from this bug

Comment 4 Satellite Program 2018-12-06 21:13:27 UTC
Upstream bug assigned to mhulan

Comment 5 Satellite Program 2018-12-06 21:13:30 UTC
Upstream bug assigned to mhulan

Comment 6 Satellite Program 2018-12-22 13:11:57 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25483 has been resolved.

Comment 9 Bryan Kearney 2019-10-22 19:51:23 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-2019:3172


Note You need to log in before you can comment on or make changes to this bug.