Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1537632

Summary: Puppet report for installer not generated due to "Invalid byte sequence in US-ASCII"
Product: Red Hat Satellite Reporter: Perry Gagne <pgagne>
Component: InstallationAssignee: Ewoud Kohl van Wijngaarden <ekohlvan>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: egolov, ehelms, ekohlvan, zhunting
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-installer-1.22.0-RC2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:47:36 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:

Comment 4 Ewoud Kohl van Wijngaarden 2018-11-20 16:33:07 UTC
Created redmine issue https://projects.theforeman.org/issues/25516 from this bug

Comment 5 Satellite Program 2018-12-06 21:04:25 UTC
Upstream bug assigned to ekohlvan

Comment 6 Satellite Program 2018-12-06 21:04:28 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25516 has been resolved.

Comment 9 Ewoud Kohl van Wijngaarden 2019-05-21 15:37:24 UTC
There was a regression which caused the checks not to be run.

Comment 11 Perry Gagne 2019-07-11 17:57:41 UTC
Verified fix in sat 6.6 snap 10

Installer prints an error when LC_ALL=C

[root@sat ~]# satellite-installer -v --scenario satellite --foreman-initial-admin-username <user> --foreman-initial-admin-password <password>
The LC_ALL environment variable should not be set to C
Your system does not meet configuration criteria
[ INFO 2019-07-11T13:53:52 verbose] Executing hooks in group pre_migrations
[ INFO 2019-07-11T13:53:52 verbose] All hooks in group pre_migrations finished
[ INFO 2019-07-11T13:53:52 verbose] Executing hooks in group boot
[ INFO 2019-07-11T13:53:52 verbose] All hooks in group boot finished
[ INFO 2019-07-11T13:53:52 verbose] Executing hooks in group init
[ INFO 2019-07-11T13:53:52 verbose] All hooks in group init finished
[ INFO 2019-07-11T13:53:52 verbose] Loading default values from puppet modules...
[ INFO 2019-07-11T13:53:52 verbose] ... finished
[ INFO 2019-07-11T13:53:52 verbose] Executing hooks in group pre_values
[ INFO 2019-07-11T13:53:52 verbose] All hooks in group pre_values finished
[ INFO 2019-07-11T13:53:52 verbose] Running installer with args [["-v", "--scenario", "satellite", "--foreman-initial-admin-username", "<user> ", "--foreman-initial-admin-password", "<password>"]]
[ INFO 2019-07-11T13:53:52 verbose] Installer finished in 2.63093212 seconds
[root@sat ~]#

Comment 12 Bryan Kearney 2019-10-22 19:47:36 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