Bug 1989143 - [e2e][automation] missing file for testing release-4.8
Summary: [e2e][automation] missing file for testing release-4.8
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.0
Assignee: Yaacov Zamir
QA Contact: Guohua Ouyang
Depends On:
Blocks: 1989152
TreeView+ depends on / blocked
Reported: 2021-08-02 14:18 UTC by Yaacov Zamir
Modified: 2021-10-18 17:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1989152 (view as bug list)
Last Closed: 2021-10-18 17:43:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 9699 0 None None None 2021-08-02 14:20:36 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:44:03 UTC

Description Yaacov Zamir 2021-08-02 14:18:08 UTC
Description of problem:
automation tests for 4.8 fail with:
error: unable to read URL "https://raw.githubusercontent.com/openshift/console/master/frontend/packages/kubevirt-plugin/integration-tests/ci-scripts/hostpath-provisioner-setup.yml", server reported 404 Not Found, status code=404

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Yaacov Zamir 2021-08-02 14:19:53 UTC
e2e test not a blocker

Comment 2 Yaacov Zamir 2021-08-02 14:50:03 UTC
moving to verified as this bug is actually on 4.8 tests and does not happen in 4.9

Comment 5 errata-xmlrpc 2021-10-18 17:43:52 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.9.0 bug fix and security 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.


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