Bug 1214832
Summary: | openshift-tc fails at boot time if node uses a bonded NIC due to init script priority | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Josep 'Pep' Turro Mauri <pep> |
Component: | Containers | Assignee: | Timothy Williams <tiwillia> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 2.2.0 | CC: | adellape, anli, bleanhar, cryan, jokerman, libra-onpremise-devel, mmccomas |
Target Milestone: | --- | Keywords: | TestCaseNeeded |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-node-1.36.2.2-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously when a bonded NIC was configured as the external interface for a node host, the network service was not started when the openshift-tc service was started. This was due to bonded NICs depending on the network service to be started, which would not start until after the openshift-tc service. This bug fix modifies the priority of the openshift-tc service on nodes to start after the network service by default. As a result, the openshift-tc service is able to start successfully on boot when a bonded interface is configured as the external interface; the network service is started first, initializing the bonded interface.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-21 19:12:21 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
Josep 'Pep' Turro Mauri
2015-04-23 15:48:50 UTC
Verified and pass 1) The chkconfig priority have been changed [root@broker init.d]# grep chkconfig network openshift-tc network:# chkconfig: 2345 10 90 openshift-tc:# chkconfig: 345 11 89 2) network can be boot. Starting monitoring for VG vg_dhcp12945: 2 logical volume(s) in volume group "vg_dhcp12945" monitored ^[[60G[^[[0;32m OK ^[[0;39m]^M Starting cgconfig service: ^[[60G[^[[0;32m OK ^[[0;39m]^M ip6tables: Applying firewall rules: ^[[60G[^[[0;32m OK ^[[0;39m]^M iptables: Applying firewall rules: ^[[60G[^[[0;32m OK ^[[0;39m]^M Bringing up loopback interface: ^[[60G[^[[0;32m OK ^[[0;39m]^M Bringing up interface bond0: Determining IP information for bond0... done. ^[[60G[^[[0;32m OK ^[[0;39m]^M 3) openshift-tc is started [root@broker init.d]# service openshift-tc status Bandwidth shaping status: qdisc htb 1: root refcnt 17 r2q 10 default 0 direct_packets_stat 2075 Sent 249309 bytes 2079 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 class htb 1:1 root prio 0 rate 800000Kbit ceil 800000Kbit burst 1600b cburst 1600b Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 0 borrowed: 0 giants: 0 tokens: 250 ctokens: 250 [OK] 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://rhn.redhat.com/errata/RHBA-2015-1463.html |