search

kubernetes-retired / poseidon

[EOL] A Firmament-based Kubernetes scheduler
http://www.firmament.io
Apache License 2.0
410 stars 79 forks source link

Duplicate AddTaskInfo call for Poseidon scheduled pods after pods move to running state #169

Closed pratikmeher44 closed 5 years ago

pratikmeher44 commented 5 years ago

AddTaskInfo should send pod information from Poseidon to Firmament only for pods scheduled by default scheduler. But AddTaskInfo is also sending pod information for pods scheduled by Poseidon. This results in duplicate addition of pod information in Firmament.

Suggestion is to filter out Poseidon scheduled running pods and send only pod information for pods scheduled by default scheduler to Firmament by AddTaskInfo call.

fejta-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

pratikmeher44 commented 5 years ago

/close

k8s-ci-robot commented 5 years ago

@pratikmeher44: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/poseidon/issues/169#issuecomment-495160192): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.