Project

General

Profile

Actions

Bug #14880

closed

arv-keepdocker is very picky about the order of its command line arguments and crashes with an obscure error if the order is wrong

Added by Julien Fouret about 5 years ago. Updated about 5 years ago.

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

Description

Hi,

I am trying to set up an arvados instance in our institution. I am having trouble to use the arv-keepdocker when setting up a compute node.

All previous step from "install" part of the documentation were OK. For information, arvados is intended to be tested on a private network so keep-proxy was not necessary.

I had some trouble with using keep storage through python SDK because I choose not to install keep-proxy for now and httplib2 from python was not parsing fine my "no_proxy" environment variable (see https://github.com/httplib2/httplib2/issues/132).

I got an error in the following step (using super_user API token from the computing node I am trying to set up (id206)):

`arv-keepdocker --project-uuid $project_uuid --pull arvados/jobs latest`

```
latest: Pulling from arvados/jobs
3d77ce4481b1: Already exists
e9d5d7a7ec48: Already exists
0275f7e96071: Already exists
e5c7ad7bde76: Already exists
354b6c89659e: Pull complete
2946e252f657: Pull complete
a58f890f60d4: Pull complete
803ff01c62a8: Pull complete
Digest: sha256:47dadb94b92346cf6adad2e11cef84331e7ee07fcef5630e12ab1cd9297938c6
Status: Downloaded newer image for arvados/jobs:latest
usage: arv-keepdocker [-h] [--version] [--normalize | --dry-run]
[--as-stream | --stream | --as-manifest | --in-manifest | --manifest | --as-raw | --raw]
[--update-collection UUID] [--use-filename FILENAME]
[--filename FILENAME] [--portable-data-hash]
[--replication N] [--storage-classes STORAGE_CLASSES]
[--threads N] [--project-uuid UUID] [--name NAME]
[--exclude PATTERN]
[--progress | --no-progress | --batch-progress]
[--silent] [--resume | --no-resume]
[--follow-links | --no-follow-links]
[--cache | --no-cache] [--retries RETRIES]
[path [path ...]]
arv-keepdocker: error: unrecognized arguments: /home/default_admin/.cache/arvados/docker/sha256:a9171d8a433188c522dfe94938afa1b8cee91635f6d281e52595e1ee09a8447c.tar
```

For information here are our DNS record (where I have replaced our institution domain name by example.org) for nodes that should be involved in the process:

core-pfx.example.org > API server
keep0-pfx.example.org > keepstore server
id206.example.org ==> compute node

This is not your convention but the DNS team for our institution does not want us to create other domains if not explicitly required by the app we deploy. We have self-signed certificate with the appropriate root and intermediate certificates installed in our servers and workstation to enable ssl authentication.

Of note `arv-put` `arv-get` are working fine on `id206.example.org`.

here is the output of `$docker version` on `id206.example.org`

```
Client:
Version: 18.09.2
API version: 1.39
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:13:47 2019
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 03:42:13 2019
OS/Arch: linux/amd64
Experimental: false
```

All OS are ubuntu 18.04 and I am using this repository for arvados `deb http://apt.arvados.org/ bionic main`

Arvados version is 1.3.0.20190211211047

Have you ever seen this error ? Do you have any idea of what is causing this ?

Thanks,


Files

system.info (1.5 KB) system.info Julien Fouret, 02/25/2019 09:26 AM

Subtasks 1 (0 open1 closed)

Task #14899: Review 14880-keepdocker-argparseResolvedPeter Amstutz03/08/2019Actions
Actions

Also available in: Atom PDF