Project

General

Profile

Actions

Bug #25516

closed

Puppet report for installer not generated due to "Invalid byte sequence in US-ASCII"

Added by Ewoud Kohl van Wijngaarden over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Installer
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Steps to Reproduce:
1. Provision a host with a fresh install and install satellite packages
2. set LC_ALL=C (via 'LC_ALL=C ssh satellite)
3. Run 'satellite-installer -v --scenario satellite --foreman-admin-username admin --foreman-admin-password changeme'

Actual results: A error is printing in the installer and no Config Management Report for the install is set to the satellite:

[ERROR 2018-01-21 16:25:23 verbose] Could not send report: invalid byte sequence in US-ASCII
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:393:in `count'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:393:in `binary?'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:283:in `visit_String'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:148:in `accept'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:503:in `block in emit_coder'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:501:in `each'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:501:in `emit_coder'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:486:in `dump_coder'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:146:in `accept'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:369:in `block in visit_Array'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:369:in `each'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:369:in `visit_Array'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:148:in `accept'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:516:in `block in dump_ivars'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:514:in `each'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:514:in `dump_ivars'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:175:in `visit_Object'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:148:in `accept'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych/visitors/yaml_tree.rb:112:in `push'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/2.1.0/psych.rb:409:in `dump'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/yaml.rb:33:in `block in dump'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:604:in `replace_file'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/yaml.rb:32:in `dump'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/yaml.rb:30:in `save'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:288:in `save'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:391:in `send_report'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:354:in `run_internal'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:306:in `override'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in `run'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:306:in `override'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `block in run'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:662:in `exit_on_fail'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `run'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
[ERROR 2018-01-21 16:25:23 verbose] /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
[ INFO 2018-01-21 16:25:23 verbose] Puppet has finished, bye!
[ INFO 2018-01-21 16:25:23 verbose] Executing hooks in group post

Expected results: No error and a config management/puppet report is set to satellite for the host (see attached screen shot for example).

Additional info: The bug does not seem to appear when you just run "satellite-installer -v" its probably best to do a fresh install and then run the installer.

Discussed with mhulan, we where wondering if there is any value in generating this installer report at all. If not, a potential fix would be to stop generating the report.

Make sure when reproducing/verifying the bug to set Org to "Any" to see its config management reports.

Actions #1

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ewoud Kohl van Wijngaarden
  • Pull request https://github.com/Katello/katello-installer/pull/715 added
Actions #2

Updated by Ewoud Kohl van Wijngaarden over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #3

Updated by John Mitsch over 5 years ago

  • Target version set to Katello 3.10.0
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF