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

Extended.deploymentconfigs with revision history limits [Conformance] should never persist more old deployments than acceptable after being observed by the controller #11114

Closed
sosiouxme opened this issue Sep 27, 2016 · 37 comments
Assignees
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2

Comments

@sosiouxme
Copy link
Member

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/6409/consoleFull had a conformance test flake:

• Failure [288.339 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:767
  with revision history limits
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:716
    should never persist more old deployments than acceptable after being observed by the controller [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:715

    Expected an error to have occurred.  Got:
        <nil>: nil

    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:696
Additional Information

This is from #11045 where I revise how the asset bundle for the console is built. I don't see how it could be related to deployments.

@sosiouxme sosiouxme added the kind/test-flake Categorizes issue or PR as related to test flakes. label Sep 27, 2016
@0xmichalis
Copy link
Contributor

@sosiouxme is this failure from 4 days ago? If so, it should be fixed on master by #11066

@mfojtik
Copy link
Member

mfojtik commented Sep 27, 2016

@sosiouxme right, this should be fixed by now, if you see this again in more recent test run feel free to re-open this.

@mfojtik mfojtik closed this as completed Sep 27, 2016
@sosiouxme
Copy link
Member Author

sorry for the false alarm.

@soltysh
Copy link
Member

soltysh commented Sep 30, 2016

This looks like a more recent run: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/6719/consoleFull although I'm wondering if that didn't fail in what I'm tracking in #11016 (comment)

@soltysh soltysh reopened this Sep 30, 2016
@soltysh
Copy link
Member

soltysh commented Sep 30, 2016

My bad, wrongly interpreted logs.

@0xmichalis
Copy link
Contributor

@enj can you post the job that failed?

@enj
Copy link
Contributor

enj commented Oct 7, 2016

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/6910/consoleFull

• Failure [486.240 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:767
  with revision history limits
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:716
    should never persist more old deployments than acceptable after being observed by the controller [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:715

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

    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:696

@soltysh
Copy link
Member

soltysh commented Oct 7, 2016

I've been hitting similar, but wrt to PodDisruptionbudget in #11187:

• Failure [80.527 seconds]
[k8s.io] DisruptionController [Feature:PodDisruptionbudget]
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:793
  should update PodDisruptionBudget status [It]
  /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/disruption.go:102

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

  /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/disruption.go:100

It all goes to #11016, I need to go back to that topic next week.

@bparees bparees reopened this Mar 1, 2017
@bparees bparees changed the title [test-flake] It should never persist more old deployments than acceptable after being observed by the controller Extended.deploymentconfigs with revision history limits [Conformance] should never persist more old deployments than acceptable after being observed by the controller Mar 1, 2017
@mfojtik
Copy link
Member

mfojtik commented Apr 26, 2017

@stevekuznetsov just saw this on GCE

@bparees
Copy link
Contributor

bparees commented Apr 27, 2017

@stevekuznetsov
Copy link
Contributor

stevekuznetsov commented Apr 27, 2017

@bparees Don't think that is the same flake -- openshift-eng/aos-cd-jobs#199 should have fixed the ETCD issue. There is no mention of credentials in the flake you linked.

@stevekuznetsov
Copy link
Contributor

stevekuznetsov commented Apr 27, 2017

@smarterclayton are we running etcd data in a tmpfs in the GCE job? If not, we will continue to see etcd issues with fsync there

@mrogers950
Copy link
Contributor

Failure [78.051 seconds]
deploymentconfigs
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:1121
  with revision history limits [Conformance]
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:892
    should never persist more old deployments than acceptable after being observed by the controller [It]
    /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:891

    the current deployment needs to have finished before attempting to trigger a new deployment through configuration change
    Expected error:
        <*errors.errorString | 0xc421861bf0>: {
            s: "found multiple running deployments: [history-limit-2 history-limit-3]",
        }
        found multiple running deployments: [history-limit-2 history-limit-3]
    not to have occurred

    /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:851

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/3885/

@tnozicka
Copy link
Contributor

Feels like this issue is tracking many different failures.

  • I guess the etcd issue is fixed now?
  • found multiple running deployments was already fixed
  • this last failure remains to be investigated

@0xmichalis
Copy link
Contributor

Different failure mode:

expected len of old deployments: 2 to equal dc revisionHistoryLimit: 3

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17104/test_pull_request_origin_extended_conformance_gce/11266/

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 7, 2018
@stevekuznetsov
Copy link
Contributor

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2
Projects
None yet
Development

No branches or pull requests