Closed dulek closed 2 years ago
@dulek: This pull request references Bugzilla bug 1997120, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (itbrown@redhat.com), skipping review request.
@dulek: all tests passed!
Full PR test history. Your PR dashboard.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dulek, MaysaMacedo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@dulek: All pull requests linked via external trackers have merged:
Bugzilla bug 1997120 has been moved to the MODIFIED state.
@dulek: Jira Issue OCPBUGS-11828: Some pull requests linked via external trackers have merged:
The following pull requests linked via external trackers have not merged:
These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh
.
Jira Issue OCPBUGS-11828 has not been moved to the MODIFIED state.
@dulek: Bugzilla bug 1997120 is in an unrecognized state (CLOSED (ERRATA)) and will not be moved to the MODIFIED state.
It can happen that we get the CNI request, but pod gets deleted before kuryr-controller was able to create KuryrPort for it. If kuryr-daemon only watches for KuryrPort events it will not be able to notice that and will wait until the timeout, which in effect doesn't play well with some K8s tests.
This commit adds a separate Service that will watch on Pod events and if Pod gets deleted we'll make sure to put a sentinel value (None) into the registry so that the thread waiting for the KuryrPort to appear there will know that it has to stop and raise an error.