Bug 1466239
| Summary: | Restart master service could not fix the invalid hostip in hostsubnet | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yan Du <yadu> | ||||
| Component: | Networking | Assignee: | Dan Winship <danw> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.6.0 | CC: | aos-bugs, bbennett, danw, eparis, xtian, yadu | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.7.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-11-28 21:59:33 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: | |||||||
| Attachments: |
|
||||||
|
Description
Yan Du
2017-06-29 10:20:11 UTC
Created attachment 1292838 [details]
masterlog
(In reply to Yan Du from comment #0) > Actual results: > The invalid hostip in hostsubnet could not be fixed after restarting master > service > > Expected results: > The invalid hostip in hostsubnet could be fixed after restarting master > service Can you be more clear about what you expected to happen and what actually happened? The current behavior seems to be that if you have an invalid HostSubnet and restart the master, then it will log an error (but continue, so that you can then fix the hostsubnet), and if you restart the node that the bad HostSubnet is assigned to, it will fail to start. I believe that behavior is correct. I wouldn't think restarting the master should make any difference. It can't know what addresses are valid on the nodes, so the old behavior was weird. However, I tried setting a bad address for a node in the hostsubnet and restarting the node process. It did not seem to detect the error. If it complained and failed to start, that would be fine. I bet this is related to the change @rchopra made to try to preserve any local address rather than always forcing one. https://github.com/openshift/origin/pull/12388 (In reply to Ben Bennett from comment #5) > I bet this is related to the change @rchopra made to try to preserve any > local address rather than always forcing one. That was my first guess too, but it's wrong. Bisecting shows it was caused by https://github.com/openshift/origin/commit/8c7065f (which messed up the SDN master's permissions), but Clayton's fix in https://github.com/openshift/origin/pull/14968 does not fix it. Still investigating. Test on latest OCP env, invalid hostip could be fixed after restart master service. openshift v3.6.133 kubernetes v1.6.1+5115d708d7 etcd 3.2.1 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-2017:3188 |