Bug 1924085 - backend tests incorrectly hard-code artifacts dir
Summary: backend tests incorrectly hard-code artifacts dir
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.6.z
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1924084
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-02 15:00 UTC by OpenShift BugZilla Robot
Modified: 2021-02-17 19:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-17 19:25:10 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 8025 0 None closed [release-4.6] Bug 1924085: don't hard-code artifact dir path 2021-02-11 14:46:39 UTC
Red Hat Product Errata RHBA-2021:0424 0 None None None 2021-02-17 19:25:32 UTC

Description OpenShift BugZilla Robot 2021-02-02 15:00:24 UTC 
+++ This bug was initially created as a clone of Bug #1924084 +++

The backend tests hard-code the artifacts directory, which causes the tests to fail in CI now that the directory has changed. This blocks any PRs from merging. We should use the $ARTIFACT_DIR env var instead.
Comment 4 Yanping Zhang 2021-02-07 09:27:42 UTC 
Checked on job history page: https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-console-release-4.6-backend, after the fix merged, there is no job failure caused by hard-code of the artifacts directory.
The bug is fixed.
Comment 6 errata-xmlrpc 2021-02-17 19:25:10 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 (OpenShift Container Platform 4.6.17 bug fix 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/RHBA-2021:0424
Note You need to log in before you can comment on or make changes to this bug.