Please create a new 64bit OS vm image so we can migrate/install buildbot-master4 on it
8 years ago
No longer depends on: 617831
bkero- from hallway conversation, current 64-bit CentOS is probably the right call here.
Assignee: server-ops-releng → bkero
dhcp/dns entries queued up for when yellow flag is raised, will commit tomorrow
I've created a CentOS 5.5 VM for this, however since buildbot-master4 already exists and is up, this is has a DHCP-assigned address from the pool. You can reach it at: email@example.com If this is going to be a more long-term situation I can put a static entry in dns/dhcp.
Can you e-mail me the root pw for this?
set to current build password
I managed to get logged in, hooray! Performance seems decent enough (120MB/sec), so let's go with this for now. Can you update the DNS entries to point buildbot-master4 at this? I can't even access the existing machine at that name....
Ok, the switch-over went perfectly. Just updated a single DHCP record and ran dhclient, now the box is up at: buildbot-master4.build.scl1.mozilla.com
handed this off, confirmed good on irc, feel free to confirm here if you like too
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
I can't see any DNS entries for this at all:  bhearsum@voot:~$ cat /etc/resolv.conf # Generated by NetworkManager search build.mozilla.org build.scl1.mozilla.com build.sjc1.mozilla.com mozilla.org mozilla.com nameserver 10.2.74.125 nameserver 10.2.74.123 nameserver 192.168.31.1 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 184.108.40.206 nameserver 220.127.116.11  bhearsum@voot:~$ host buildbot-master4.build.scl1.mozilla.com hoHost buildbot-master4.build.scl1.mozilla.com not found: 3(NXDOMAIN)  bhearsum@voot:~$ host buildbot-master4.build.mozilla.org host bHost buildbot-master4.build.mozilla.org not found: 3(NXDOMAIN)  bhearsum@voot:~$ host buildbot-master04.build.scl1.mozilla.com Host buildbot-master04.build.scl1.mozilla.com not found: 3(NXDOMAIN)  bhearsum@voot:~$ host buildbot-master04.build.mozilla.org Host buildbot-master04.build.mozilla.org not found: 3(NXDOMAIN)  bhearsum@voot:~$ host 10.12.51.235 Host 18.104.22.168.in-addr.arpa. not found: 3(NXDOMAIN) It should have: buildbot-master4.build.scl1.mozilla.com (A record) buildbot-master04.build.mozilla.org (CNAME to the above) Reverse DNS pointing to the scl1 name
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Sorry about that, I reused the old buildbot-master4 DNS entry, which zandr later repurposed back to the original host. I thought the old hardware was gone permanently. I've created some new DNS records, and altered the DHCP records. The host is online now, please confirm. [bkero@boris ~]$ host buildbot-master4.build.scl1.mozilla.com buildbot-master4.build.scl1.mozilla.com has address 10.12.48.18 [bkero@boris ~]$ host 10.12.48.18 22.214.171.124.in-addr.arpa domain name pointer buildbot-master4.build.scl1.mozilla.com. [bkero@boris ~]$ host buildbot-master4.build.mozilla.org buildbot-master4.build.mozilla.org is an alias for buildbot-master4.build.scl1.mozilla.com. buildbot-master4.build.scl1.mozilla.com has address 10.12.48.18
Yup, everything looks good!
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago → 8 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.