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

Using optr.queue.ShutDown directly as upstream K8s is fixed now #339

Merged

Conversation

LalatenduMohanty
Copy link
Member

@LalatenduMohanty LalatenduMohanty commented Mar 20, 2020

Upstream pull request kubernetes/kubernetes#77170. It is available in upstream v1.15

Signed-off-by: Lalatendu Mohanty lmohanty@redhat.com

Upstream pull request kubernetes/kubernetes#77170

Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 20, 2020
@LalatenduMohanty LalatenduMohanty changed the title [WIP] Using optr.queue.ShutDown directly as upstream K8s is fixed now Using optr.queue.ShutDown directly as upstream K8s is fixed now Mar 24, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 24, 2020
@wking
Copy link
Member

wking commented Mar 24, 2020

Upstream PR vendored in here with 0672262 (#249).

/lgtm

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 24, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

19 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@abhinavdahiya
Copy link
Contributor

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, LalatenduMohanty, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [abhinavdahiya,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

14 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@sdodson
Copy link
Member

sdodson commented Mar 27, 2020

/hold
@LalatenduMohanty can you please look into why the integration tests started failing on March 20th and haven't passed since? There was one pass on this commit so I don't know if it's this PR or a general failure.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 27, 2020
@LalatenduMohanty
Copy link
Member Author

@LalatenduMohanty can you please look into why the integration tests started failing on March 20th and haven't passed since? There was one pass on this commit so I don't know if it's this PR or a general failure.

Last time I checked the failure looked like a flake, but this time it is

2020/03/27 19:16:22 Container bin-cli in pod integration completed successfully
2020/03/27 19:16:35 Container bin-hyperkube in pod integration completed successfully
2020/03/27 21:16:18 error: unable to signal to artifacts container to terminate in pod integration, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2020/03/27 21:16:19 error: unable to retrieve artifacts from pod integration: could not read gzipped artifacts: unable to upgrade connection: container not found ("artifacts")
2020/03/27 21:16:19 error: could not wait for pod 'integration': it is no longer present on the cluster (usually a result of a race or resource pressure. re-running the job should help)
2020/03/27 21:16:19 No custom metadata found and prow metadata already exists. Not updating the metadata.
E0327 21:16:19.074027      13 event.go:263] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:".160045c47c0d14b3", GenerateName:"", Namespace:"ci-op-gtgb1drn", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"", Namespace:"ci-op-gtgb1drn", Name:"", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"CiJobFailed", Message:"Running job pull-ci-openshift-cluster-version-operator-master-integration for PR https://github.com/openshift/cluster-version-operator/pull/339 in namespace ci-op-gtgb1drn from author LalatenduMohanty", Source:v1.EventSource{Component:"ci-op-gtgb1drn", Host:""}, FirstTimestamp:v1.Time{Time:time.Time{wall:0xbf97b928c1e176b3, ext:7317917608909, loc:(*time.Location)(0x271e5e0)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0xbf97b928c1e176b3, ext:7317917608909, loc:(*time.Location)(0x271e5e0)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'events ".160045c47c0d14b3" is forbidden: unable to create new content in namespace ci-op-gtgb1drn because it is being terminated' (will not retry!)
2020/03/27 21:16:20 Ran for 2h1m58s
error: could not run steps: step integration failed: template pod "integration" failed: pod was deleted while ci-operator step was waiting for it

looking in to it

@LalatenduMohanty
Copy link
Member Author

/retest

@LalatenduMohanty
Copy link
Member Author

LalatenduMohanty commented Mar 31, 2020

Another run, but the issue is same https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-version-operator/339/pull-ci-openshift-cluster-version-operator-master-integration/826

2020/03/31 14:48:56 Container bin-hyperkube in pod integration completed successfully
2020/03/31 16:48:34 error: unable to signal to artifacts container to terminate in pod integration, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2020/03/31 16:48:34 error: unable to retrieve artifacts from pod integration: could not read gzipped artifacts: unable to upgrade connection: container not found ("artifacts")
2020/03/31 16:48:34 error: could not wait for pod 'integration': it is no longer present on the cluster (usually a result of a race or resource pressure. re-running the job should help)
2020/03/31 16:48:34 No custom metadata found and prow metadata already exists. Not updating the metadata.
E0331 16:48:34.053496      15 event.go:263] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:".1601717a55d8cd21", GenerateName:"", Namespace:"ci-op-2kbnlkt3", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"", Namespace:"ci-op-2kbnlkt3", Name:"", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"CiJobFailed", Message:"Running job pull-ci-openshift-cluster-version-operator-master-integration for PR https://github.com/openshift/cluster-version-operator/pull/339 in namespace ci-op-2kbnlkt3 from author LalatenduMohanty", Source:v1.EventSource{Component:"ci-op-2kbnlkt3", Host:""}, FirstTimestamp:v1.Time{Time:time.Time{wall:0xbf98faf8830f7921, ext:7245935993107, loc:(*time.Location)(0x271e640)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0xbf98faf8830f7921, ext:7245935993107, loc:(*time.Location)(0x271e640)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'events ".1601717a55d8cd21" is forbidden: unable to create new content in namespace ci-op-2kbnlkt3 because it is being terminated' (will not retry!)
2020/03/31 16:48:35 Ran for 2h0m46s
error: could not run steps: step integration failed: template pod "integration" failed: pod was deleted while ci-operator step was waiting for it 

@LalatenduMohanty
Copy link
Member Author

/retest

@LalatenduMohanty
Copy link
Member Author

@sdodson The e2e tests has passed now, we should remove the hold

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 16, 2020
@sdodson
Copy link
Member

sdodson commented Apr 16, 2020

/hold cancel
No need to block on me if the tests are passing now.

@LalatenduMohanty
Copy link
Member Author

/retest

2 similar comments
@LalatenduMohanty
Copy link
Member Author

/retest

@LalatenduMohanty
Copy link
Member Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit b8af7e4 into openshift:master Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants