Bug 1833436 - Sriov tests remove all the sriov networks / sriov network configuration crs
Summary: Sriov tests remove all the sriov networks / sriov network configuration crs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Federico Paolinelli
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-08 16:36 UTC by Federico Paolinelli
Modified: 2020-07-13 17:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:36:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 203 0 None closed Bug 1833436: Focus the cleanup only on sriov networks / policies created by the tests 2020-06-24 02:13:46 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:36:34 UTC

Description Federico Paolinelli 2020-05-08 16:36:12 UTC 
Description of problem:


With the current implementation, sriov tests clean the sriov networks / network configurations in order to start from a clean slate. This may be a problem once those tests are consumed by cnf tests and ran against a configured cluster.

What we want is to have those tests clean only the configurations they applied.
Comment 1 Federico Paolinelli 2020-05-08 20:39:28 UTC 
The impact here is only on the test suite.
Comment 4 zhaozhanqi 2020-05-12 12:59:19 UTC 
Verified this bug
Comment 5 errata-xmlrpc 2020-07-13 17:36:23 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:2409
Note You need to log in before you can comment on or make changes to this bug.