Bug 1775055 - OSP CI bootstrap log collection fails with "'ascii' codec can't encode characters"
Summary: OSP CI bootstrap log collection fails with "'ascii' codec can't encode charac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.3.0
Assignee: Tomas Sedovic
QA Contact: David Sanz
URL:
Whiteboard:
Depends On:
Blocks: 1775062
TreeView+ depends on / blocked
 
Reported: 2019-11-21 11:47 UTC by Tomas Sedovic
Modified: 2020-01-23 11:13 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1775062 (view as bug list)
Environment:
Last Closed: 2020-01-23 11:13:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 2631 0 'None' 'closed' 'OpenStack: Use UTF-8 locales in CI container image' 2019-12-04 10:37:21 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:13:54 UTC

Description Tomas Sedovic 2019-11-21 11:47:42 UTC
Description of problem:

The CI for the OpenStack provider is able to gather logs of the bootstrap Nova server in order to investigate the boot/Ignition logs.

For example this log should have the server boot sequence:

https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.2/237/artifacts/e2e-openstack-serial/bootstrap/nova.log

Actual results:

The bootstrap/nova.log file collected and stored by the CI only contains this line:

'ascii' codec can't encode characters in position 28961-28963: ordinal not in range(128)


Expected results:

The file would contain the full contents of the Nova boot log.

Comment 1 Tomas Sedovic 2019-11-21 11:50:40 UTC
Fixed in: https://github.com/openshift/installer/pull/2631

Comment 4 errata-xmlrpc 2020-01-23 11:13: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/RHBA-2020:0062


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