Autotest DUT - Chameleon Creation should not be blocked on re-using a DNS entry |
||||
Issue descriptionCurrently if there's an old DNS entry for a chameleon device it blocks the creation DUT in Autotest. Can we just instead flag multiple warnings instead? This bug has cropped up quite a bit and while there's a fix we can make it less painful. https://sites.google.com/a/google.com/englabs/resources/infrastructure/chromeos/chromeos-infrastructure/servers/dns/DNS-Server-Tools/nsupdate Previous bugs https://bugs.chromium.org/p/chromium/issues/detail?id=509140 https://bugs.chromium.org/p/chromium/issues/detail?id=541332 https://bugs.chromium.org/p/chromium/issues/detail?id=478833
,
Aug 30 2016
Richard, is this related to your deployment script? Any advice?
,
Aug 30 2016
Does flushing the DNS cache in the lab help?
,
Sep 6 2016
You can flush the DNS on the workstation but there is no guarantee when the DNS update takes effect. Typically it ranges from 5 to 120 minutes after a DNS flush for the setting to properly take since workstations use Corp controlled DNS servers and not the labs. Potentially it can be almost a day...
,
Sep 7 2016
Seems useful, marking as FixIt & updating title
,
Sep 9 2016
The site has been moved so this is where to do the fix https://sites.google.com/a/google.com/englab-dev/resources/infrastructure/chromeos/chromeos-infrastructure/servers/dns/DNS-Server-Tools/nsupdate
,
Sep 9 2016
,
Mar 10 2018
This bug has not been touched in over a year. It is probably no longer relevant. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dshi@chromium.org
, Aug 25 2016