Bug #16343: [controller] bad routing of container_requests#create call when LoginCluster is in use - Arvados

Actions

Copy link

Bug #16343

closed

[controller] bad routing of container_requests#create call when LoginCluster is in use

Added by Tom Clegg over 4 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Tom Clegg

Category:

API

Target version:

2020-05-06 Sprint

Start date:

04/28/2020

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Story points:

Release:

Arvados 2.0.3

Release relationship:

Auto

Description

In source:lib/controller/fed_containers.go a "create container request" call is supposed to be handled as a local request when no remote cluster ID is specified.

However, when LoginCluster is in use, local tokens have a UUID indicating the LoginCluster's ID, not the local cluster's ID, and this causes the "short circuit to local API server" condition to be missed. The request does ends up being directed to the correct (local) cluster, but it goes through the "remote" code path, which depends on the local cluster's config having a RemoteClusters entry for itself.

This should be fixed so it doesn't depend on having a "self" entry in RemoteClusters.

Subtasks 1 (0 open — 1 closed)