Bug 1933878 - [sig-devex][Feature:JenkinsRHELImagesOnly][Slow] openshift pipeline build Sync plugin tests using the ephemeral template
Summary: [sig-devex][Feature:JenkinsRHELImagesOnly][Slow] openshift pipeline build Sy...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Jenkins
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Akram Ben Aissi
QA Contact: Jitendar Singh
URL:
Whiteboard:
: 1938311 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-01 22:33 UTC by Rashmi Gottipati
Modified: 2021-06-18 17:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-devex][Feature:JenkinsRHELImagesOnly][Slow] openshift pipeline build Sync plugin tests using the ephemeral template
Last Closed: 2021-06-18 17:24:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rashmi Gottipati 2021-03-01 22:33:59 UTC
test:
[sig-devex][Feature:JenkinsRHELImagesOnly][Slow] openshift pipeline build  Sync plugin tests using the ephemeral template 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-devex%5C%5D%5C%5BFeature%3AJenkinsRHELImagesOnly%5C%5D%5C%5BSlow%5C%5D+openshift+pipeline+build++Sync+plugin+tests+using+the+ephemeral+template


Job ID: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

Error from the job log:
Mar  1 18:59:18.999: INFO: Unexpected error occurred: timed out waiting for the condition
[AfterEach] [sig-instrumentation] Prometheus
  github.com/openshift/origin/test/extended/util/client.go:138
STEP: Collecting events from namespace "e2e-test-prometheus-pgmj6".
STEP: Found 8 events.
Mar  1 18:59:19.137: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for execpod: { } Scheduled: Successfully assigned e2e-test-prometheus-pgmj6/execpod to libvirt-s390x-0-4-c4b-xbx9k-worker-0-zjn4p
skipped 12 lines unfold_more
  github.com/openshift/origin/test/extended/util/client.go:139
STEP: Destroying namespace "e2e-test-prometheus-pgmj6" for this suite.
fail [k8s.io/kubernetes.0/test/e2e/framework/pod/resource.go:483]: failed to create new exec pod in namespace: e2e-test-prometheus-pgmj6
Unexpected error:
    <*errors.errorString | 0xc0002d29b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
failed: (5m21s) 2021-03-01T18:59:19 "[sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early] [Suite:openshift/conformance/parallel]"
started: (1/5/18) "[sig-devex][Feature:JenkinsRHELImagesOnly][Slow] openshift pipeline build  Sync plugin tests using the ephemeral template"
skipped 619 lines unfold_more
[sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early] [Suite:openshift/conformance/parallel]
[sig-instrumentation][Late] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Suite:openshift/conformance/parallel]
Writing JUnit report to /tmp/artifacts/junit/junit_e2e_20210301-192106.xml
error: 2 fail, 16 pass, 0 skip (27m7s)
2021/03/01 19:21:11 Container test in pod jenkins-e2e failed, exit code 1, reason Error
2021/03/01 19:25:28 Copied 96.40MB of artifacts from jenkins-e2e to /logs/artifacts/e2e-remote-libvirt
2021/03/01 19:25:28 Releasing leases for "e2e-remote-libvirt"
2021/03/01 19:25:28 Releasing lease for "libvirt-s390x-quota-slice": libvirt-s390x-0-4
2021/03/01 19:25:28 No custom metadata found and prow metadata already exists. Not updating the metadata.
2021/03/01 19:25:29 Ran for 1h24m36s
error: some steps failed:
  * could not run steps: step e2e-remote-libvirt failed: template pod "jenkins-e2e" failed: the pod ci-op-dk1sxn6w/jenkins-e2e failed after 1h22m6s (failed containers: test): ContainerFailed one or more containers exited
Container test exited with code 1, reason Error
---
jn4p container/agnhost-container reason/NotReady
skipped 19 lines unfold_more
[sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early] [Suite:openshift/conformance/parallel]
[sig-instrumentation][Late] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Suite:openshift/conformance/parallel]
Writing JUnit report to /tmp/artifacts/junit/junit_e2e_20210301-192106.xml
error: 2 fail, 16 pass, 0 skip (27m7s)
---

Comment 1 Jakub Hadvig 2021-03-08 15:54:47 UTC
Moving this issue to Jenkins team for further investigation, since the issue is with the JenkinsRHELImages.

Comment 2 Adam Kaplan 2021-06-18 17:24:26 UTC
This does not appear to be widespread any longer - the only instance of the failure I see in the past week is related to Z tests:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-remote-libvirt-jenkins-e2e-s390x-4.8/1405888271350763520

Comment 3 Adam Kaplan 2021-06-18 17:53:06 UTC
*** Bug 1938311 has been marked as a duplicate of this bug. ***


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