Closed shiftstack-merge-bot[bot] closed 1 year ago
Hi @shiftstack-merge-bot[bot]. Thanks for your PR.
I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/retest no pods created? retrying...
@shiftstack-merge-bot[bot]: all tests passed!
Full PR test history. Your PR dashboard.
@shiftstack-merge-bot[bot]: This pull request references Jira Issue OCPBUGS-12780, which is valid. The bug has been moved to the POST state.
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request.
The bug has been updated to refer to the pull request using the external bug tracker.
@shiftstack-merge-bot[bot]: This pull request references Jira Issue OCPBUGS-12780, which is valid.
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request.
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dulek, shiftstack-merge-bot[bot]
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@shiftstack-merge-bot[bot]: Jira Issue OCPBUGS-12780: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-12780 has been moved to the MODIFIED state.
/cherry-pick release-4.13
@dulek: new pull request created: #726
It can happen that during the cleanup of KuryrPort when Pod is already gone we'll fail trying to find the parent port ID. We have a bug that in this case finalizing of KuryrPort fails.
This commit changes the way we look for the hostIP of the pod to actually look up a node using the info from KuryrPort CRD. If this fails (node removed?) we try querying OpenStack API to get this information. If this fails too, we just don't pass hostIP to mocked Pod.