New issue
Advanced search Search tips

Issue 631555 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

cros: flash: support ipv6 address

Project Member Reported by gwendal@chromium.org, Jul 26 2016

Issue description

In the lab, DUT ipv4 addresses keep changing, but as Kevin suggested, we can use static ipv6 address.

To use them with cros flash, we can do run  
cros flash ssh://[2620:0:1000:1305:250:b6ff:fe63:478a] <image>

but cros_flash.py complains the address is not pingable.
in chromite/lib/remote_access.py, Pingable() run ping, even if the address is an ipv6 address.

Instead, of ping/ping6, we should install nc (net-analyzer/openbsd-netcat) and run 'nc -w <timeout> -z <address> 22'. Not only it will check is the DUT is pingable, but if we can ssh it as well.
 
Given 'cros flash --no-ping ssh://[2620:0:1000:1305:250:b6ff:fe63:478a] <image>' mostly works, it is a P3 bug, although using nc instead of ping throughout would be nice. 
Components: Build
Labels: -Build-Toolchain
Status: Available (was: Untriaged)
so we just need to run `ping6` instead of `ping` when we have an IPv6 address.

this doesn't help when given a hostname that only has AAAA records though ...
It would be nice if more of these commands (particularly `cros deploy` and `update_kernel.sh`) could fall back to sping, or look up Hostname's from ~/.ssh/config, to make it easy to use symbolic hostnames that aren't in the DNS.
i don't think sping makes that much sense as that only works on internal Google systems and requires making a full ssh connection (which the ping is trying to triage ahead of time)

Comment 5 Deleted

Cc: -cernekee@chromium.org
Components: -Build Infra>Client>ChromeOS>Build
Status: Available (was: Untriaged)
Status: Fixed (was: Available)
i recall this being fixed, but i can't find the CLs off hand.  if it's still failing, please reopen.

Sign in to add a comment