Project

General

Profile

Actions

Bug #17682

closed

[arvados-client] shell stutter

Added by Ward Vandewege almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Release relationship:
Auto

Description

When connecting via a container request UUID, the "connecting to container ..." line is printed twice:

$ ./arvados-client shell ce8i5-xvhdp-e6wnujfslyyqn4b 
connecting to container ce8i5-dz642-h1cl0sa62d4i430
connecting to container ce8i5-dz642-h1cl0sa62d4i430
root@0f13dcd755fa:~# 

When using the container request, nothing like that is printed:

$ ./arvados-client shell ce8i5-dz642-h1cl0sa62d4i430
root@0f13dcd755fa:~# 

Subtasks 1 (0 open1 closed)

Task #17730: Review 17682-fix-stutterResolvedTom Clegg05/26/2021Actions

Related issues

Related to Arvados Epics - Idea #17207: External access to web services running in containersNewActions
Actions #1

Updated by Ward Vandewege almost 3 years ago

  • Related to Idea #17207: External access to web services running in containers added
Actions #2

Updated by Ward Vandewege almost 3 years ago

  • Description updated (diff)
Actions #3

Updated by Ward Vandewege almost 3 years ago

  • Description updated (diff)
Actions #4

Updated by Ward Vandewege almost 3 years ago

  • Description updated (diff)
Actions #5

Updated by Tom Clegg almost 3 years ago

As a side effect, this fix also avoids an extra API call and avoids the possibility, when a container request UUID is supplied, of setting up a "probe" tunnel to container A and then (due to cancel/retry) setting up the real tunnel to a different container B. (This seems pretty harmless but could produce mildly confusing results.)

17682-fix-stutter @ e9ab3d864a8deb2810d7a49b0529a2aef0c0b41c -- developer-run-tests: #2480

Actions #6

Updated by Tom Clegg almost 3 years ago

  • Assigned To set to Tom Clegg
  • Status changed from New to In Progress
Actions #7

Updated by Ward Vandewege almost 3 years ago

Tom Clegg wrote:

As a side effect, this fix also avoids an extra API call and avoids the possibility, when a container request UUID is supplied, of setting up a "probe" tunnel to container A and then (due to cancel/retry) setting up the real tunnel to a different container B. (This seems pretty harmless but could produce mildly confusing results.)

17682-fix-stutter @ e9ab3d864a8deb2810d7a49b0529a2aef0c0b41c -- developer-run-tests: #2480

LGTM, thanks!

Actions #8

Updated by Tom Clegg almost 3 years ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by Peter Amstutz over 2 years ago

  • Release set to 41
Actions

Also available in: Atom PDF