Bug 1775055

Summary: OSP CI bootstrap log collection fails with "'ascii' codec can't encode characters"
Product: OpenShift Container Platform Reporter: Tomas Sedovic <tsedovic>
Component: InstallerAssignee: Tomas Sedovic <tsedovic>
Installer sub component: OpenShift on OpenStack QA Contact: David Sanz <dsanzmor>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: high    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1775062 (view as bug list) Environment:
Last Closed: 2020-01-23 11:13: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:
Bug Depends On:    
Bug Blocks: 1775062    

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 2 Tomas Sedovic 2019-11-21 11:55:25 UTC 
The bootstrap logs are now being gathered properly:

https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-4.3/432/artifacts/e2e-openstack/bootstrap/nova.log
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