Flake: error: update acceptor rejected failing-dc-mid-1: pods for rc "failing-dc-mid-1" took longer than 20 seconds to become ready

[pospispa]

There was no error output from the command.
Running test/end-to-end/core.sh:435: executing 'oc logs --previous dc/failing-dc-mid' expecting success and text 'test mid hook executed'...
SUCCESS after 0.336s: test/end-to-end/core.sh:435: executing 'oc logs --previous dc/failing-dc-mid' expecting success and text 'test mid hook executed'
Standard output from the command:
--> mid: Running hook pod ...
test mid hook executed
--> mid: Success
--> Scaling failing-dc-mid-1 to 2
--> Waiting up to 20s for pods in rc failing-dc-mid-1 to become ready
error: update acceptor rejected failing-dc-mid-1: pods for rc "failing-dc-mid-1" took longer than 20 seconds to become ready

There was no error output from the command.
[INFO] Run pod diagnostics
Running test/end-to-end/core.sh:439: executing 'oadm diagnostics DiagnosticPod --images='openshift/origin-${component}:b013f00'' expecting success and text 'Running diagnostic: PodCheckDns'...
FAILURE after 4.613s: test/end-to-end/core.sh:439: executing 'oadm diagnostics DiagnosticPod --images='openshift/origin-${component}:b013f00'' expecting success and text 'Running diagnostic: PodCheckDns': the output content test failed
Standard output from the command:
[Note] Determining if client configuration exists for client/cluster diagnostics
Info:  Successfully read a client config file at '/tmp/openshift/test-end-to-end/openshift.local.config/master/admin.kubeconfig'

[Note] Running diagnostic: DiagnosticPod
       Description: Create a pod to run diagnostics from the application standpoint
       
Info:  Output from the diagnostic pod (image openshift/origin-deployer:b013f00):
       [Note] Running diagnostic: PodCheckAuth
              Description: Check that service account credentials authenticate as expected
       
[Note] Summary of diagnostics execution (version v3.6.0-alpha.1+b013f00-997):
[Note] Completed with no errors or warnings seen.

There was no error output from the command.
[ERROR] PID 371: hack/lib/cmd.sh:241: `return "${return_code}"` exited with status 1.
[INFO] 		Stack Trace: 
[INFO] 		  1: hack/lib/cmd.sh:241: `return "${return_code}"`
[INFO] 		  2: test/end-to-end/core.sh:439: os::cmd::expect_success_and_text
[INFO]   Exiting with code 1.
[ERROR] PID 31244: hack/test-end-to-end-docker.sh:52: `${OS_ROOT}/test/end-to-end/core.sh` exited with status 1.
[INFO] 		Stack Trace: 
[INFO] 		  1: hack/test-end-to-end-docker.sh:52: `${OS_ROOT}/test/end-to-end/core.sh`
[INFO]   Exiting with code 1.

Full console output: https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/880/consoleFull#26721763658b6e51eb7608a5981914356

[mfojtik]

@tnozicka can you please triage this?

[mfojtik]

This seems to be really a diagnostics flake, not deployment flake based on the comments in the test:

# Requires a node to run the origin-deployer pod; expects registry deployed, deployer image pulled
# TODO: Find out why this would flake expecting PodCheckDns to run
# https://github.com/openshift/origin/issues/9888
#os::cmd::expect_success_and_text 'oadm diagnostics DiagnosticPod --images='"'""${USE_IMAGES}""'" 'Running diagnostic: PodCheckDns'

@bparees feel free to re-assign to whoever owns the oc diagnostics nowadays ;-)

[bparees]

@bparees feel free to re-assign to whoever owns the oc diagnostics nowadays ;-)

reassigning to @nobody....

[bparees]

confirmed customer success team owns oc diagnostics.

[brenton]

@sosiouxme, would you mind taking a look at this check again?

[sosiouxme]

It seems like a dupe of ye olde flake #9888

The workaround for that was merged June 9 (after this issue).