Closed
Bug 733275
Opened 13 years ago
Closed 13 years ago
adding an interface removes sticky interface routes
Categories
(Infrastructure & Operations :: Infrastructure: Other, task)
Infrastructure & Operations
Infrastructure: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: bhourigan)
Details
If you add a new interface to a system with network::vlan, the network subsystem gets restarted, and the ip route tables get deleted.
This is easy to forget and accidentally un-stick all of the interfaces on e.g., an admin host.
Currently, puppet-{iproute,iprule} get run via rc.local. Is there a network initscript they could be attached to, instead?
Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-infra → bhourigan
Assignee | ||
Comment 1•13 years ago
|
||
:dustin
I have an idea for a fix, is there a particular host that this can be tested on?
Reporter | ||
Comment 2•13 years ago
|
||
I don't have one, but certainly we could spin up a VM. There are a few VMs on KVM right now that are just there to generate load - we could use one of those. Find me in IRC when you want to try.
Assignee | ||
Comment 3•13 years ago
|
||
I saw this scroll by earlier on irc, the standard RHEL6 /etc/sysconfig/network-scripts/ifup-post script supports local network up/down hooks.
/sbin/ifup-local $DEVICE
/sbin/ifdown-local $DEVICE
It gets executed automatically if it exists and is +x
Assignee | ||
Comment 4•13 years ago
|
||
Deployed fix, tested on admin1b.private.pek1.
[root@admin1b.private.pek1 ~]# ip route show table 70
10.24.70.0/24 dev bond0.70 scope link
default via 10.24.70.1 dev bond0.70
[root@admin1b.private.pek1 ~]# service network restart
Shutting down interface bond0.70: [ OK ]
Shutting down interface bond0.74: [ OK ]
Shutting down interface bond0.75: [ OK ]
Shutting down interface bond0.77: [ OK ]
Shutting down interface bond0.8: [ OK ]
Shutting down interface bond0.80: [ OK ]
Shutting down interface bond0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
Bringing up interface bond0.70: [ OK ]
Bringing up interface bond0.74: [ OK ]
Bringing up interface bond0.75: [ OK ]
Bringing up interface bond0.77: [ OK ]
Bringing up interface bond0.8: [ OK ]
Bringing up interface bond0.80: [ OK ]
[root@admin1b.private.pek1 ~]# ip route show table 70
10.24.70.0/24 dev bond0.70 scope link
default via 10.24.70.1 dev bond0.70
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•13 years ago
|
||
Just wanted to mention - this fix works on both RHEL5 and RHEL6
Updated•12 years ago
|
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•