Infrastructure » sepia

dubia001 appears to be running openstack. It's unreachable but ethtool via SOL indicates its NIC isn't connected. Will check cable next time I'm at the DC

dubia002 appears to be in rough shape. hostname reports to be backup01

General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and reboot the system.
sulogin: cannot open password database!
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1: Inode 7 has illegal block(s).  

/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)
[    8.867764] sulogin[355]: segfault at 8 ip 00000000004017d0 sp 00007fff0a5fba30 error 4 in sulogin[400000+3000]
Segmentation fault

dubia003 is jenkins
dubia004 is pulpito

dubia001 can be repurposed from openstack if it hasn't been reused already. I was the one using it for openstack testing a long time ago.

https://github.com/ceph/ceph-sepia-secrets/pull/77

PR is merged

dubia003 is jenkins, and should rename
dubia004 is pulpito and paddles, and should be renamed

mira123 (formerly dubia001) is full of healthy 4TB drives
mira124 (formerly dubia002)'s disks are almost all bad

dubia003 and 004 have been renamed in DNS and cleaned up from ansible inventory
https://github.com/ceph/ceph-sepia-secrets/pull/79
https://github.com/ceph/ceph-sepia-secrets/pull/80

mira123 is now "store02" and will be redundant storage backend for RHEV cluster.

Replaced drive 4 in jenkins. Its RAID is degraded and underlying data may be lost. I can't get smart data from the drives because any attempt at reading from them results in an I/O error. I can't imagine anyone's actually using this host given its poor health...

RAID is rebuilding now. sdb is readonly and throwing errors to console.

jenkins.front can be repurposed

7OCT2016 - Just shut it down.