Bug 1894860

Summary: 'backend' CI job passing despite failing tests
Product: OpenShift Container Platform Reporter: Predrag Knezevic <pknezevi>
Component: Management ConsoleAssignee: Predrag Knezevic <pknezevi>
Status: CLOSED ERRATA QA Contact: Yanping Zhang <yanpzhan>
Severity: high Docs Contact:
Priority: high    
Version: 4.7CC: aos-bugs, jokerman, spadgett, yapei
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1894868 (view as bug list) Environment:
Last Closed: 2021-02-24 15:31:24 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: 1894868    

Description Predrag Knezevic 2020-11-05 10:00:16 UTC
Description of problem:

'backend' CI job triggered on each PR is passing despite failing tests. For example:

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/7099/pull-ci-openshift-console-master-backend/1323911973502455808

Comment 1 Samuel Padgett 2020-11-05 14:39:59 UTC
I think this was introduced by https://github.com/openshift/console/pull/6400

We don't have `set -o pipefail` set, so apparently `go test -v "${COVER}" "$@" "${TEST[@]}" 2>&1 | tee /tmp/artifacts/test.out` doesn't fail.

Comment 3 Yanping Zhang 2020-11-12 08:12:40 UTC
Checked job history, now there are failed jobs and passed jobs: https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-console-master-backend
The bug is fixed.

Comment 6 errata-xmlrpc 2021-02-24 15:31:24 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633