Bug 1709664
| Summary: | Update cluster.spec.kubernetesApiEndpoints.serverEndpoints.serverAddress to an invalid address, the federatedcluster status still is Ready | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> | |
| Component: | Federation | Assignee: | Paul Morie <pmorie> | |
| Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> | |
| Severity: | low | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.0 | CC: | bmcelvee, mnewby, nagrawal | |
| Target Milestone: | --- | |||
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1760271 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:28:42 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: | 1760271 | |||
This is the same issue as https://github.com/kubernetes-sigs/kubefed/issues/878. We will be fixing it for the upstream beta. This issue was fixed upstream by https://github.com/kubernetes-sigs/kubefed/pull/943, and the fix was released as of rc3. Verified with KubeFed controller-manager version: version.Info{Version:"v4.2.0", GitCommit:"ee84d241d0d8038640f9dad7cbeb0ea8cce58b6c", GitTreeState:"clean", BuildDate:"2019-08-06T15:32:52Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Does this bug require doc text? The Doc Type/Text field is not currently set. Thanks! 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:2922 |
Description of problem: Update cluster.spec.kubernetesApiEndpoints.serverEndpoints.serverAddress to an invalid address, the federatedcluster status still is Ready Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-05-09-204138 True False 3h24m Cluster version is 4.1.0-0.nightly-2019-05-09-204138 Federation v2 controller-manager version: version.Info{Version:"v0.0.8", GitCommit:"0d12bc3d438b61d9966c79a19f12b01d00d95aae", GitTreeState:"clean", BuildDate:"2019-04-11T04:57:35Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} How reproducible: Always Steps to Reproduce: 1. Install federation v2 contfoller manager from operator hub 2. Join a cluster to federation 3. Check federatedcluster $ oc get federatedcluster NAME READY cluster1 True 4. Modify the cluster.spec.kubernetesApiEndpoints.serverEndpoints.serverAddress to an invalid address $ oc get cluster cluster1 -ojson|jq .spec.kubernetesApiEndpoints.serverEndpoints[].serverAddress "https://test.invalid.com" 5. Check federatedcluster Actual results: After 10 minutes $ oc get federatedcluster NAME READY cluster1 True Expected results: Cluster1 status changes to "Offline" Additional info: If restart controller manager, federatedcluster status can be changed. $ oc get federatedcluster NAME READY cluster1 $ oc get federatedcluster cluster1 -ojson|jq .status { "conditions": [ { "lastProbeTime": "2019-05-14T06:36:54Z", "lastTransitionTime": "2019-05-14T06:36:13Z", "message": "cluster is not reachable", "reason": "ClusterNotReachable", "status": "True", "type": "Offline" } ] }