Bug 1732582

Summary: image stream import integration tests aren't testing valid configuration
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: ImageStreamsAssignee: Oleg Bulatov <obulatov>
Status: CLOSED DEFERRED QA Contact: XiuJuan Wang <xiuwang>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: adam.kaplan, aos-bugs, jokerman, mmccomas, wzheng
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: Environment:
Last Closed: 2019-11-01 20:57:00 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:

Description David Eads 2019-07-23 19:23:59 UTC
Existing integration tests do not test valid configuration modes or mechanisms for the OCM.  They rely on modes of wiring that have not been valid since 3.11 and are now impossible to wire. The tests should either be unit tests checking the behavior of specific pieces or e2e tests checking wiring.  These are the final integration tests being snipped today:

  TestImageStreamImport
  TestImageStreamImportAuthenticated
  TestImageStreamImportOfMultiSegmentDockerReference
  TestImageStreamImportOfV1ImageFromV2Repository
  TestImageStreamImportScheduled
  TestImageStreamImportTagsFromRepository
  TestRegistryWhitelistingValidation

Comment 1 David Eads 2019-07-24 14:10:38 UTC
A handy link to the final state of test-integration: https://github.com/openshift/origin/tree/ac77c8a2e1f2b93131daca15d1fdbeb8832840e7/test/integration

Comment 2 Adam Kaplan 2019-07-30 19:45:15 UTC
@Oleg a similar card is being tracked on JIRA: https://jira.coreos.com/browse/DEVEXP-392

Comment 3 Adam Kaplan 2019-08-23 13:53:25 UTC
Targeting 4.3 - we will likely want to backport to 4.2.z only.

Comment 4 Adam Kaplan 2019-11-01 20:57:00 UTC
Oleg did a deep dive on this, and identified several areas to port over that DevEx is tracking in JIRA:

https://jira.coreos.com/browse/DEVEXP-450
https://jira.coreos.com/browse/DEVEXP-451
https://jira.coreos.com/browse/DEVEXP-452
https://jira.coreos.com/browse/DEVEXP-453