Page MenuHomePhabricator

codfw: new mw servers not getting an IP when default to Stretch
Closed, ResolvedPublic

Description

I did the installation of 18 new mw servers yesterday using Buster in T241852 and @MoritzMuehlenhoff pointed out that we need to install Stretch on those servers. I changed the DHCP file for those servers to Stretch and tried to install 2 servers mw2310 and mw2311 it wouldn't pass the network configuration step.

Details

Related Gerrit Patches:

Event Timeline

Papaul created this task.Feb 6 2020, 1:23 AM
Restricted Application added a project: Operations. · View Herald TranscriptFeb 6 2020, 1:23 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Papaul triaged this task as Medium priority.Feb 6 2020, 1:23 AM

Change 570587 had a related patch set uploaded (by Muehlenhoff; owner: Muehlenhoff):
[operations/puppet@production] Switch mw2311 to stretch bootif tftpboot environment

https://gerrit.wikimedia.org/r/570587

Change 570587 merged by Muehlenhoff:
[operations/puppet@production] Switch mw2311 to stretch bootif tftpboot environment

https://gerrit.wikimedia.org/r/570587

Papaul added a comment.Feb 6 2020, 3:47 PM

Did the re-install on mw2311 it works . Thanks

The ethernet adapter is slightly different than the BCM5720 we otherwise already run on stretch. E.g. on ms-be2050 it reports as

Broadcom Limited NetXtreme BCM5720 Gigabit Ethernet PCIe

while on the new mw hosts it's showing up as

Dell NetXtreme BCM5720 2-port Gigabit Ethernet PCIe

The "2-port" makes me think that we might run into a similar installer issue as we recently did with some of the DB/es hosts. I merged a patch to switch mw2311 to the same d-i environment we used to install the es2 hosts.

MoritzMuehlenhoff closed this task as Resolved.Feb 7 2020, 8:19 AM

This is confirmed working by Papaul when using the stretch-bootif tftpboot environment, closing.