cautotest: can't reach live logs for running jobs on shardless hosts |
|||||
Issue descriptionIt looks like when I attempt to access logs for jobs in flight, such as currently-running repair attempts, cautotest redirects me to Pantheon to look for logs even though the test has not yet been uploaded to Pantheon. The proper behavior would be for the link to test logs to hit local storage for running tests and tests whose logs have not yet been collected by the gsoffloader. This has been the case for awhile, but the Jetstream devices were previously on a shard. When I accessed the logs via the shard directly, that worked, so I think this may be an issue only on shardless hosts. An example of an affected host is: https://ubercautotest.corp.google.com/afe/#tab_id=view_host&object_id=5962
,
Mar 17 2017
I don't think it is desired for gale to be not sharded if Whirlwind is on a shard. I think Whirlwind and Gale could/should be on the same shard. Putting Gale on a shard would effectively solve the problem for me since I'd be able to access the logs from the shard and wouldn't need to worry about the gs_offloader log race.
,
Mar 20 2017
Sounds like we should add gale to a shard. I believe "atest shard add_boards ..." is the way to do this, though I don't see any documentation on our sites page that spells it out. Assigning to deputy, cc'ing shard expert.
,
Mar 20 2017
The command to add a board to a shard is: $ cd AUTOTEST $ cli/atest shard add_boards -l <label> <shard> For this specific case: $ cli/atest shard add_boards -l 'board:gale' <shard_hostname_you_pick>
,
Apr 13 2017
Passing to current deputy.
,
Apr 17 2017
One of my Gales is failing repairs today and I was somewhat inconvenienced by this issue.
,
Jul 25 2017
,
May 15 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by akes...@chromium.org
, Mar 17 2017