Bug 1762787
Summary: | Kuryr: Failures releasing port when pod doesn't have status.hostIP set | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Michał Dulko <mdulko> | |
Component: | Networking | Assignee: | Michał Dulko <mdulko> | |
Networking sub component: | kuryr | QA Contact: | Jon Uriarte <juriarte> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | medium | |||
Priority: | high | CC: | juriarte | |
Version: | 4.2.0 | |||
Target Milestone: | --- | |||
Target Release: | 4.3.0 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1762788 (view as bug list) | Environment: | ||
Last Closed: | 2020-01-23 11:07:51 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1762788 |
Description
Michał Dulko
2019-10-17 13:31:42 UTC
Verified on OCP 4.3.0-0.nightly-2019-10-18-051534 build on top of OSP 13 2019-10-01.1 puddle. release image: registry.svc.ci.openshift.org/ocp/release@sha256:2a8f99a817784b303bd76706e14b23cffd98fca1e96b672dfb0b534a79ec5a86 The next warning log has been caught during openshift-tests execution: WARNING kuryr_kubernetes.controller.drivers.vif_pool [-] Pod pod-update-activedeadlineseconds-5f983277-f1bd-11e9-8a12-525400903b5b does not have status.hostIP field set when getting deleted. This is unusual. Trying to determine the IP by calling Neutron. And kuryr-controller still remains "alive" so it was not restarted: INFO werkzeug [-] 192.168.0.17 - - [18/Oct/2019 15:40:05] "GET /alive HTTP/1.1" 200 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062 |