Bug 1852995

Summary:	[Feature:DeploymentConfig] deploymentconfigs adoption [Conformance] will orphan all RCs and adopt them back when recreated
Product:	OpenShift Container Platform	Reporter:	Corey Daley <cdaley>
Component:	openshift-controller-manager	Assignee:	Adam Kaplan <adam.kaplan>
Status:	CLOSED DUPLICATE	QA Contact:	wewang <wewang>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.z	CC:	aos-bugs, maszulik, mfojtik, wking
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	workloads
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[Feature:DeploymentConfig] deploymentconfigs adoption [Conformance] will orphan all RCs and adopt them back when recreated
Last Closed:	2020-07-02 08:09:36 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 Corey Daley 2020-07-01 17:27:37 UTC

test:
[Feature:DeploymentConfig] deploymentconfigs adoption [Conformance] will orphan all RCs and adopt them back when recreated 

is failing frequently in CI, see search results:
https://search.svc.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5BFeature%3ADeploymentConfig%5C%5D+deploymentconfigs+adoption+%5C%5BConformance%5C%5D+will+orphan+all+RCs+and+adopt+them+back+when+recreated

https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.4/1278326021912793088

Comment 1 W. Trevor King 2020-07-02 04:34:14 UTC

Opened against 4.2, which is almost EOL, but linked example job is 4.4.0-0.ci-2020-07-01-060254 [1]?  Also a number of previous bugs around this test-case, including the fixed-in-4.3-but-not-backported bug 1795629 and the 4.5 bug 1852916 which you also opened today (which links a 4.5 cluster-bot job).  The failure message in this bug's 4.4 example job is:

fail [github.com/openshift/origin/test/extended/deployments/deployments.go:1699]: Unexpected error:
    <*errors.errorString | 0xc0002851c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

which is not all that helpful.  Stdout for that test-case has a lot of chatter, and I can't separate the signal from the noise.  So... maybe this should be a bug to improve the failure message for 4.4+?  Or close it as a dup of bug 1852916?  Or...?

[1]: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.4/1278326021912793088#1:build-log.txt%3A12

Comment 2 Maciej Szulik 2020-07-02 08:09:36 UTC


*** This bug has been marked as a duplicate of bug 1852916 ***