Bug 1317835
Summary: | Update host for route doesn't take effect | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yan Du <yadu> |
Component: | Networking | Assignee: | Maru Newby <mnewby> |
Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | aos-bugs, bmeng, mnewby, tdawson |
Version: | 3.2.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 16:32:54 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: |
Description
Yan Du
2016-03-15 10:25:10 UTC
I can reproduce. The edit to the route is successful, and the router picks up the edit and reconfigures itself for the new hostname. However, 'oc get route' prefers the host of the ingress status which is not being updated when the host of a route changes. I have a partial diagnosis. When the status plugin encounters a route for the first time it writes the update time to its timestamp cache with nanosecond precision, but the ingress timestamp is not stored with nanosecond precision. When the host for the route is subsequently updated, the status plugin finds the most recent ingress timestamp to not match its cached timestamp and, assuming this to mean that another route has updated the ingress status, does not update the ingress status for the route with the updated host. Bouncing the router pod with 'oc dc router --latest' clears the router's timestamp cache and all subsequent router updates are correctly handled by the status plugin. I'm assuming the fix is truncating the nanosecond portion of timestamps before they are stored in the status plugin's timestamp cache, but need to confirm this. The origin PR has merged. This has been merged into OSE and is in release v3.2.0.8 Test on latest ose env openshift v3.2.0.8 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 Issue have been fixed, route could be updated successfully, move bug to verified 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/RHSA-2016:1064 |