Bug 1728518
| Summary: | [SDN] Node doesn't get un-taint when MTU value is fixed | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anurag saxena <anusaxen> |
| Component: | Networking | Assignee: | Ricardo Carrillo Cruz <ricarril> |
| Status: | CLOSED ERRATA | QA Contact: | Anurag saxena <anusaxen> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | aos-bugs, danw, ricarril, zzhao |
| 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: | Environment: | ||
| Last Closed: | 2019-10-16 06:33:23 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
Anurag saxena
2019-07-10 06:12:30 UTC
(In reply to Anurag saxena from comment #0) > 4. Systemctl Start NetworkManager <<< This should enable dhcp and corrects > the > MTU value as default > > Actual results: 4th step corrects set the MTU value back to 9001 but node > remains Tainted > > > Expected results: Node should get un-taint when MTU value is fixed The taint doesn't need to be removed until OpenShift SDN is restarted. (In reply to Dan Winship from comment #1) > (In reply to Anurag saxena from comment #0) > > 4. Systemctl Start NetworkManager <<< This should enable dhcp and corrects > > the > > MTU value as default > > > > Actual results: 4th step corrects set the MTU value back to 9001 but node > > remains Tainted > > > > > > Expected results: Node should get un-taint when MTU value is fixed > > The taint doesn't need to be removed until OpenShift SDN is restarted. Hmm..i tried to kill openshift-sdn process post step 4.Openshift-sdn got restarted but following remained the same $ oc describe nodes ip-10-0-132-170.ap-northeast-1.compute.internal | grep -i sch Taints: network.openshift.io/mtu-too-small=value:NoSchedule <<<<<<<<<<<<<<<< Unschedulable: false No, I mean, with the current state of the code, the taint never gets removed, but with the fixed version, the expected behavior will be that it gets removed after restart, not that it gets removed immediately. (In reply to Dan Winship from comment #3) > No, I mean, with the current state of the code, the taint never gets > removed, but with the fixed version, the expected behavior will be that it > gets removed after restart, not that it gets removed immediately. Got it. Thanks for clarification, Dan. Thanks for the fix! This works okay now following steps mentioned in comment 1 and the restarting openshift-sdn Steps from comment 1 tainted the node to NoSchedule [core@ip-10-0-x-x ~]$ oc describe nodes ip-10-0-130-153.ap-northeast-1.compute.internal | grep -i sch Taints: network.openshift.io/mtu-too-small=value:NoSchedule Unschedulable: false Post openshift-sdn restart, node got untainted: [core@ip-10-0-x-x ~]$ oc describe nodes ip-10-0-130-153.ap-northeast-1.compute.internal | grep -i sch Unschedulable: false Verifying based on above checks. 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 |