Project

General

Profile

Actions

Bug #59206

open

cephadm source on github

Added by Riaan pretorius about 1 year ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Description

I downloaded the cephadm pythion script from github and tried a deploy. This happens:

Adding key to root@localhost authorized_keys...
Adding host zacptprsvmrs01.localdomain...
Deploying mon service with default placement...
Deploying mgr service with default placement...
Deploying crash service with default placement...
Deploying ceph-exporter service with default placement...
Non-zero exit code 22 from /usr/bin/podman run --rm --ipc=host --stop-signal=SIGTERM --net=host --entrypoint /usr/bin/ceph --init -e CONTAINER_IMAGE=europe-west4-docker.pkg.dev/customdock/rke2-docker-images/ceph/ceph:v17 -e NODE_NAME=zacptprsvmrs01.localdomain -e CEPH_USE_RANDOM_NONCE=1 -v /var/log/ceph/70bd5ab2-cd6c-11ed-b539-b68c24932762:/var/log/ceph:z -v /tmp/ceph-tmppmu4omnl:/etc/ceph/ceph.client.admin.keyring:z -v /tmp/ceph-tmpx902eb90:/etc/ceph/ceph.conf:z europe-west4-docker.pkg.dev/customdock/rke2-docker-images/ceph/ceph:v17 orch apply ceph-exporter
/usr/bin/ceph: stderr Error EINVAL: Usage:
/usr/bin/ceph: stderr   ceph orch apply -i <yaml spec> [--dry-run]
/usr/bin/ceph: stderr   ceph orch apply <service_type> [--placement=<placement_string>] [--unmanaged]
/usr/bin/ceph: stderr
Traceback (most recent call last):
  File "/usr/local/bin/cephadm", line 9669, in <module>
    main()
  File "/usr/local/bin/cephadm", line 9657, in main
    r = ctx.func(ctx)
  File "/usr/local/bin/cephadm", line 2221, in _default_image
    return func(ctx)
  File "/usr/local/bin/cephadm", line 5790, in command_bootstrap
    prepare_ssh(ctx, cli, wait_for_mgr_restart)
  File "/usr/local/bin/cephadm", line 5291, in prepare_ssh
    cli(['orch', 'apply', t])
  File "/usr/local/bin/cephadm", line 5730, in cli
    ).run(timeout=timeout, verbosity=verbosity)
  File "/usr/local/bin/cephadm", line 4161, in run
    desc=self.entrypoint, timeout=timeout, verbosity=verbosity)
  File "/usr/local/bin/cephadm", line 1869, in call_throws
    raise RuntimeError('Failed command: %s' % ' '.join(command))
RuntimeError: Failed command: /usr/bin/podman run --rm --ipc=host --stop-signal=SIGTERM --net=host --entrypoint /usr/bin/ceph --init -e CONTAINER_IMAGE=europe-west4-docker.pkg.dev/customdock/rke2-docker-images/ceph/ceph:v17 -e NODE_NAME=zacptprsvmrs01.localdomain -e CEPH_USE_RANDOM_NONCE=1 -v /var/log/ceph/70bd5ab2-cd6c-11ed-b539-b68c24932762:/var/log/ceph:z -v /tmp/ceph-tmppmu4omnl:/etc/ceph/ceph.client.admin.keyring:z -v /tmp/ceph-tmpx902eb90:/etc/ceph/ceph.conf:z europe-west4-docker.pkg.dev/customdock/rke2-docker-images/ceph/ceph:v17 orch apply ceph-exporter

Then i installed the RPM version and it does not do that error

Actions #1

Updated by John Mulligan about 1 year ago

Please share the exact URL that you downloaded the cephadm script from.
Please share the exact command line arguments you passed to the script (anonymize them if needed).

Actions #2

Updated by Adam King about 1 year ago

  • Project changed from Ceph to Orchestrator
  • Category deleted (ceph cli)

Hi, so this was an issue with a mismatch between the cephadm binary in the quincy branch and the quincy image being used that we unfortunately introduced when adding in the ceph-exporter service. It tries to setup a ceph-exporter service by default, but quincy images before 17.2.6 don't know what that is, resulting in this failure. Just before writing this I merged a patch for this issue (https://github.com/ceph/ceph/pull/50904) so if you re-pull the cephadm binary from the quincy branch and try again it should work. Otherwise, if you pass --skip-monitoring-stack during bootstrap it should also avoid this issue. You could then manually apply the other monitoring services that are actually in the quincy image being used (should be alertmanager, prometheus, node-exporter, and grafana) if you want them.

Actions #3

Updated by Adam King about 1 year ago

  • Assignee set to Adam King
  • Pull request ID set to 50548
Actions #4

Updated by Riaan pretorius about 1 year ago

Adam King wrote:

Hi, so this was an issue with a mismatch between the cephadm binary in the quincy branch and the quincy image being used that we unfortunately introduced when adding in the ceph-exporter service. It tries to setup a ceph-exporter service by default, but quincy images before 17.2.6 don't know what that is, resulting in this failure. Just before writing this I merged a patch for this issue (https://github.com/ceph/ceph/pull/50904) so if you re-pull the cephadm binary from the quincy branch and try again it should work. Otherwise, if you pass --skip-monitoring-stack during bootstrap it should also avoid this issue. You could then manually apply the other monitoring services that are actually in the quincy image being used (should be alertmanager, prometheus, node-exporter, and grafana) if you want them.

@Adam DC949 thank you for the prompt response. Will check it out :)

Actions #5

Updated by Ilya Dryomov 11 months ago

  • Target version deleted (v17.2.6)
Actions

Also available in: Atom PDF