Project

General

Profile

Actions

Bug #45696

closed

cephadm: Validate bootstrap dashboard "key" and "cert" file exists

Added by Ricardo Marques almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ricardo Marques
Category:
cephadm (binary)
Target version:
% Done:

0%

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

Description

While bootstrapping a cluster, I've provided "--dashboard-key" and "--dashboard-crt" options pointing to files that do not exist:

cephadm --verbose bootstrap --mon-ip 10.20.36.200 --dashboard-key cert/not_exists.key --dashboard-crt cert/not_exists.crt

The bootstrap proceeds and only failed in the end, after deploy containers:

INFO:cephadm:/usr/bin/ceph:stderr Error: error checking path "/root/cert/not_exists.crt": stat /root/cert/not_exists.crt: no such file or directory
Traceback (most recent call last):
  File "/usr/sbin/cephadm", line 4655, in <module>
    r = args.func()
  File "/usr/sbin/cephadm", line 1153, in _default_image
    return func()
  File "/usr/sbin/cephadm", line 2618, in command_bootstrap
    cli(['dashboard', 'set-ssl-certificate', '-i', '/tmp/dashboard.crt'], extra_mounts=mounts)
  File "/usr/sbin/cephadm", line 2450, in cli
    ).run(timeout=timeout)
  File "/usr/sbin/cephadm", line 2183, in run
    self.run_cmd(), desc=self.entrypoint, timeout=timeout)
  File "/usr/sbin/cephadm", line 837, in call_throws
    raise RuntimeError('Failed command: %s' % ' '.join(command))
Actions #1

Updated by Ricardo Marques almost 4 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Ricardo Marques almost 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 35229
Actions #3

Updated by Ricardo Marques almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Sebastian Wagner almost 4 years ago

  • Status changed from Pending Backport to Resolved
  • Target version set to v15.2.4
Actions #5

Updated by Sebastian Wagner almost 4 years ago

  • Status changed from Resolved to Pending Backport
Actions #6

Updated by Sebastian Wagner almost 4 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF