679818 - w64-ix-slave04.winbuild.scl1.mozilla.com has no dns entries

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Armen [:armenzg]]

Now that we have a bunch of win64 slaves I don't need anymore this slave which was setup by hand.

Please reimage it whenever you can. What hostname should we give to it?

zandr mentioned in bug 670761#c39 that slaves 01,03,04 and 05 were repurposed as masters. Should we use any of those slave # or go at the end of the list with w64-ix-slave43?

This machine is also on mtv and *not* part of the winbuild network.

Comment 1

[Armen [:armenzg]]

Feel free to do also w64-ix-ref unless you find a reason not to (digipengi mentioned on IRC that we don't really need a ref machine anymore).

Comment 2

[Zandr Milewski [:zandr]]

mw64-ix-slave01 is in MV and hasn't been upgraded yet. If it were up to me, I'd throw it at the end of the mw32 pool.

w64-ix-ref is in MV, and would be fine to replace one of the low-numbered slaves that was repurposed.

Comment 3

[Zandr Milewski [:zandr]]

(In reply to Zandr Milewski [:zandr] from comment #2)

> w64-ix-ref is in MV

It's in SCL1. Rest of the paragraph still applies (good replacement)

Comment 4

[Armen [:armenzg]]

Plan works for me. Feel free to adjust summary.

Comment 5

[Amy Rich [:arr] [:arich]]

I've reinstalled mw64-ix-slave01 as mw32-ix-slave26, and it is ready for releng to do postimage/puppetization.  mlarrain, I'll let you handle reimaging w64-ix-ref as a w64-ix-slave (01, 03, 04, or 05).

Comment 6

[Matthew Larrain[:MaRu]]

I will make it w64-ix-slave03.

Comment 7

[Matthew Larrain[:MaRu]]

scratch that I will make it w64-ix-slave04

Comment 8

[Matthew Larrain[:MaRu]]

I need sw-3a.scl1:19 moved over to vlan 40

Comment 9

[Dustin J. Mitchell [:dustin] (he/him)]

sw-3a.scl1:19 is already on vlan40:

sw-3a.scl1# sh vlan 40
...
  Port Information Mode     Unknown VLAN Status    
  ---------------- -------- ------------ ----------
  19               Untagged Learn        Up

Comment 10

[Matthew Larrain[:MaRu]]

Machine has been reimaged as w64-ix-slave04 and is ready for armen to drop it back into the pool.

Comment 11

[Armen [:armenzg]]

Can I get some help on reaching w64-ix-slave04?
I also can't reach it with w64-ix-slave04-mgmt.build.scl1.mozilla.com

armenzg-laptop $ host w64-ix-slave04.build
Host w64-ix-slave04.build not found: 3(NXDOMAIN)

Comment 12

[Amy Rich [:arr] [:arich]]

Armen, all the w64-ix-slave machines are in winbuild.scl1.mozilla.com. That said, there doesn't appear to be a dns entry for the host or the management port.  Matt, can you please take a look on the windows servers?

Comment 13

[Matthew Larrain[:MaRu]]

the dns entry for the IP that w64-ix-slave04 was using was set to w64-ix-ref I changed it to w64-ix-slave04 and will reboot the machine. Should be working shortly.

Comment 14

[Matthew Larrain[:MaRu]]

Upon further investagation Amy and I found that the TTL is set to an hour so after that the host will be available assuming it was cached prior to that.