Project

General

Profile

Actions

Bug #51277

closed

cephadm bootstrap: unable to set up admin label

Added by Melissa Li almost 3 years ago. Updated almost 3 years ago.

Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
cephadm
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I try to run bootstrap like so:

`curl --silent --remote-name --location https://github.com/ceph/ceph/raw/pacific/src/cephadm/cephadm`
`chmod +x cephadm`
`sudo ./cephadm bootstrap --mon-ip 127.0.0.1 --ssh-private-key /home/melissali/.ssh/id_rsa --skip-mon-network --skip-monitoring-stack --single-host-defaults --skip-dashboard --allow-fqdn-hostname`

And I get this error:

```
Adding host localhost.localdomain...
Deploying mon service with default placement...
Deploying mgr service with default placement...
Deploying crash service with default placement...
Enabling client.admin keyring and conf on hosts with "admin" label
Non-zero exit code 22 from /bin/docker run --rm --ipc=host --stop-signal=SIGTERM --net=host --entrypoint /usr/bin/ceph --init -e CONTAINER_IMAGE=docker.io/ceph/ceph:v16 -e NODE_NAME=localhost.localdomain -e CEPH_USE_RANDOM_NONCE=1 -v /var/log/ceph/43ccdbb6-d07c-11eb-bcaf-080027df1efa:/var/log/ceph:z -v /tmp/ceph-tmp_gxxvt2e:/etc/ceph/ceph.client.admin.keyring:z -v /tmp/ceph-tmp6y2s3cb_:/etc/ceph/ceph.conf:z docker.io/ceph/ceph:v16 orch client-keyring set client.admin label:_admin
/usr/bin/ceph: stderr Invalid command: client-keyring not in start|stop|restart|redeploy|reconfig
/usr/bin/ceph: stderr orch start|stop|restart|redeploy|reconfig <service_name> :  Start, stop, restart, redeploy, or reconfig an entire service (i.e. all daemons)
/usr/bin/ceph: stderr Error EINVAL: invalid command
Unable to set up "admin" label; assuming older version of Ceph
```

I noticed another person also had this issue: https://www.spinics.net/lists/ceph-users/msg66874.html


Related issues 1 (0 open1 closed)

Related to Orchestrator - Bug #51258: cephadm bootstrap: applying host specs suddenly removes the admin keyring from bootstrap hostResolved

Actions
Actions #1

Updated by Sebastian Wagner almost 3 years ago

  • Description updated (diff)
Actions #2

Updated by Adam King almost 3 years ago

I feel like this is the correct behavior. The current v16 image (https://hub.docker.com/layers/ceph/ceph/v16/images/sha256-a4614b35b6763a5aa9b4c4c4916d6858841097610ac487daf70bd13e8fb79a0b?context=explore) that is pulled is the same as the v16.2.4 image. It doesn't look like the admin label stuff got into 16.2.4. However, the cephadm binary being pulled directly off github here is just the latest pacific, which does have the admin label changes. Once a new pacific build is created and the v16 image is updated this should all work fine (last time it was built as of now was May 13th). In the meantime trying to see if we can setup the label and then just logging and moving on if we can't feels like the correct way to handle the mismatch between the up-to-date binary on the pacific branch and the slightly older v16 image.

Actions #3

Updated by Sebastian Wagner almost 3 years ago

  • Related to Bug #51258: cephadm bootstrap: applying host specs suddenly removes the admin keyring from bootstrap host added
Actions #4

Updated by Sebastian Wagner almost 3 years ago

  • Status changed from New to Can't reproduce
Actions

Also available in: Atom PDF