Project

General

Profile

Actions
Copy link

Bug #57387

open

Bootstrapping with custom registry should set mgr config keys

Added by Voja Molani over 1 year ago. Updated 10 months ago.

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

0%

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

Description

Bootstrapping a cluster using a custom registry, with options --registry-url --registry-username --registry-password given to cephadm bootstrap should set the relevant mgr configuration keys mgr/cephadm/registry_url, mgr/cephadm/registry_username and mgr/cephadm/registry_password, respectively.

Currently using a custom registry is very cumbersome when neither cephadm bootstrap nor cephadm registry-login actually set these configuration keys, making deployment fail on any subsequent server with a registry pull error.

Actions
Copy link

Also available in: Atom PDF