Bug 1762788
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: | gcheresh, juriarte, ltomasbo |
Version: | 4.2.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.2.z | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1762787 | Environment: | |
Last Closed: | 2019-10-30 04:45:14 UTC | Type: | --- |
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: | 1762787 | ||
Bug Blocks: |
Description
Michał Dulko
2019-10-17 13:33:49 UTC
Verified on OCP 4.2.0-0.nightly-2019-10-25-021846 build on top of OSP 13 2019-10-01.1 puddle. release image: registry.svc.ci.openshift.org/ocp/release@sha256:8f97aa21e1c0b2815ec7c86e4138362940a5dcbc292840ab4d6d5b67fedb173f The next warning log has been caught during openshift-tests execution: 2019-10-25 13:57:07.948 1 WARNING kuryr_kubernetes.controller.drivers.vif_pool [-] Pod pod-update-activedeadlineseconds-286b28d2-f72f-11e9-b339-525400903b5b does not have status.hostIP field set when getting del│eted. This is unusual. Trying to determine the IP by calling Neutron. And kuryr-controller still remains "alive" so it was not restarted: 2019-10-25 13:57:08.827 1 INFO werkzeug [-] 192.168.0.22 - - [25/Oct/2019 13:57:08] "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-2019:3151 |