-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Comments
@sosiouxme is this failure from 4 days ago? If so, it should be fixed on master by #11066 |
@sosiouxme right, this should be fixed by now, if you see this again in more recent test run feel free to re-open this. |
sorry for the false alarm. |
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) |
My bad, wrongly interpreted logs. |
@enj can you post the job that failed? |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/6910/consoleFull
|
I've been hitting similar, but wrt to PodDisruptionbudget in #11187:
It all goes to #11016, I need to go back to that topic next week. |
@stevekuznetsov just saw this on GCE |
@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. |
@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 |
|
Feels like this issue is tracking many different failures.
|
Different failure mode:
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/close |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/6409/consoleFull had a conformance test flake:
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.
The text was updated successfully, but these errors were encountered: