New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 636573 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Repair Failed services

Project Member Reported by tienchang@chromium.org, Aug 10 2016

Issue description

chromeos3-row3-rack2-rpm1 is not pingable, causing test failures. This is the PDU in Chaos. Please investigate.

Traceback message from weekly run. http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=72224206
TestError: ('The AP was not configured because the PDU is down. See the ERROR log for more details.\n%s', "{'2.4 GHz MAC Address': 'a0:f3:c1:37:40:86',\n '5 GHz MAC Address': 'N/A',\n 'Controller class': 'StaticAPConfigurator',\n 'Hostname': 'chromeos3-row3-rack2-host11',\n 'Router name': 'wr740nv4'}")
 

Comment 1 by jongkyuj@google.com, Aug 11 2016

Status: Started (was: Assigned)
chromeos3-row3-rack2-rpm1 is not reachable by host or IP.
The Ethernet link is there from the unit but might need to reboot.

Comment 2 by jongkyuj@google.com, Aug 11 2016

Status: Fixed (was: Started)
The host is pingable now.

jongkyuj@jongkyuj0:~$ ping chromeos3-row3-rack2-rpm1
PING chromeos3-row3-rack2-rpm1.cros.corp.google.com (172.22.38.10) 56(84) bytes of data.
64 bytes from 172.22.38.10: icmp_seq=1 ttl=253 time=2.86 ms
64 bytes from 172.22.38.10: icmp_seq=2 ttl=253 time=1.13 ms
64 bytes from 172.22.38.10: icmp_seq=3 ttl=253 time=1.74 ms

Comment 3 by jongkyuj@google.com, Aug 11 2016

Status: Verified (was: Fixed)
jongkyuj@jongkyuj0:~$ ping 172.22.38.10
PING 172.22.38.10 (172.22.38.10) 56(84) bytes of data.
64 bytes from 172.22.38.10: icmp_seq=1 ttl=253 time=1.21 ms
64 bytes from 172.22.38.10: icmp_seq=2 ttl=253 time=3.60 ms

Sign in to add a comment