Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[templates] templateinstance readiness test [It] should report ready soon after all annotated objects are ready #15901

Closed
bparees opened this issue Aug 22, 2017 · 7 comments
Assignees
Labels
component/templateservicebroker kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@bparees
Copy link
Contributor

bparees commented Aug 22, 2017

[templates] templateinstance readiness test
/go/src/github.com/openshift/origin/test/extended/templates/templateinstance_readiness.go:193
  should report ready soon after all annotated objects are ready [It]
  /go/src/github.com/openshift/origin/test/extended/templates/templateinstance_readiness.go:142

  Expected error:
      <*errors.errorString | 0xc42026f540>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  not to have occurred

  /go/src/github.com/openshift/origin/test/extended/templates/templateinstance_readiness.go:125

https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_templates/69

Guessing this is a flake since it runs as part of the merge queue, so it shouldn't have been explicitly broken by anything.

@jim-minter
Copy link
Contributor

jim-minter commented Aug 22, 2017

On https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_templates/69, AFAICS, cakephp-mysql-example-1-hook-pre terminated successfully, but nothing happened next. Master logs are missing so can't diagnose further.

@bparees
Copy link
Contributor Author

bparees commented Aug 22, 2017

any debug we should add to the test to better dump the various pod states/information when this fails in the future?

@jim-minter
Copy link
Contributor

On https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_templates/754/, the build failed due to being unable to push to the registry. Master logs missing. #15903.

@jim-minter
Copy link
Contributor

any debug we should add to the test to better dump the various pod states/information when this fails in the future?

possibly, but I'm going to attack getting the master logs first.

@bparees
Copy link
Contributor Author

bparees commented Aug 22, 2017

dunno that there's anything more useful in this one, but it looks like the same failure occurred here:
https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_templates/68/

@jim-minter
Copy link
Contributor

On https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_templates/68/ the build failed for some reason. openshift-eng/aos-cd-jobs#581 re-added the master log collection. I'll add dumping of the build & deploy states to this job as well.

@jim-minter
Copy link
Contributor

I believe these issues were fixed by #15966

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/templateservicebroker kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

2 participants