Bug #21658
open`arvados-client logs` shows no logs then exits zero
Description
I am looking for more information about why dispatcher tried and failed to kill a running container (the hello-world container from arvados-client diagnostics
). See the final container request record and arvados-dispatch-cloud logs attached. I ran:
% arvados-client logs z2a07-xvhdp-vu3d9kdg4hcgmdi connected, polling for log data from container z2a07-dz642-fcdoi6pbsnakqkc
The tool then immediately exits with code 0 and no other output, which leaves me confused.
The best case scenario is it's showing no logs because there are no logs to show (log_uuid
is null). In that case, the message is confusing. Why does it say it's polling if there's nothing to poll? What is it connected to?
The worse case is that there actually is something it should show me and it's just not. If it's running into trouble there should be an error message and a nonzero exit status.
Files