470
edits
m (→Kitten) |
m (→Kitten) |
||
| Line 200: | Line 200: | ||
python kitten.py <hostname> | python kitten.py <hostname> | ||
Example output (lines numbers added for reference): | |||
1 talos-r3-xp-013: enabled | |||
2 farm: moz | |||
3 colo: scl1 | |||
4 distro: winxp | |||
5 pool: tests-scl1-windows | |||
6 trustlevel: try | |||
7 master: bm16-tests1-windows | |||
8 fqdn: talos-r3-xp-013.build.scl1.mozilla.com. | |||
9 PDU?: False | |||
10 IPMI?: False | |||
11 reachable: True | |||
12 buildbot: running; active; job 1 minute ago | |||
13 tacfile: found | |||
14 lastseen: 1 minute ago | |||
15 master: buildbot-master16.build.scl1.mozilla.com | |||
1. hostname and it's status according to slavealloc | |||
2. farm: aws or moz | |||
3. colo: what colo the host is located (from slavealloc) | |||
4. distro: what OS distribution slavealloc lists | |||
5. pool: what build/test pool slavealloc lists | |||
6. trustlevel: the host's trustlevel per slavealloc | |||
7. master: the master that slavealloc lists for the host | |||
8. fqdn: the FQDN that was returned from the DNS lookup | |||
9. PDU?: does Inventory (or tegras.json) list a PDU for this host | |||
10. IPMI?: does a -mgmt DNS entry exist for this host | |||
11. Was briarpatch able to successfully ping and SSH to the host | |||
12. buildbot: the status of buildbot and what the last activity was | |||
13. tacfile: was a buildbot.tac file found | |||
14. lastseen: the timestamp of the last entry in twistd.log | |||
15. master: what the buildbot.tac file lists as the host's master | |||
Example of a host that cannot be reached: | |||
(production)[buildduty@cruncher production]$ python kitten.py -v talos-r3-xp-019 | (production)[buildduty@cruncher production]$ python kitten.py -v talos-r3-xp-019 | ||
talos-r3-xp-019: enabled | talos-r3-xp-019: enabled | ||
farm: moz | farm: moz | ||
edits