Bug #15126
closedRename NIC1 to eth0 on CentOS testnodes
0%
Description
Freshly installed testnodes (mira and smithi) are left with their primary NIC in a down state at the end of an ansible run.
Presumably this is because there's ansible logic in place for Ubuntu machines to set eth0 via DHCP.
In RHEL/CentOS, network --bootproto=dhcp --device=eth0 --onboot=on
in the kickstart has taken care of this.
New udev naming rules break this.
Updated by David Galloway about 8 years ago
- Blocks Bug #15120: smithis with bad rpmdbs added
Updated by David Galloway about 8 years ago
- Status changed from New to Won't Fix
I was mistaken. This is not the case.
What was happening was our DHCP server was handing out a 2 hour lease.
Our testnodes got kickstarted in EDT and then changed to UTC during the initial ansible run.
2 hours pass and the system never tries to renew its DHCP lease because the time it's expecting never happens.
Instead, we've opted to change our default DHCP lease time to 12 hours.