Ceph request to get keyring / ceph status fails on Nautilus
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned |
Bug Description
root@juju-
ceph version 14.2.1 (d555a9489eb35f
# What's in /var/lib/ceph/mon/ ?
root@juju-
ceph-juju-
# Ask Ceph for the client.osd-upgrade key:
root@juju-
2019-08-15 14:59:33.511 7f6f93b95700 -1 auth: unable to find a keyring on /var/lib/
2019-08-15 14:59:33.511 7f6f93b95700 -1 AuthRegistry(
exported keyring for client.osd-upgrade
[client.
key = AQDJb1VduEKkIhA
caps mon = "allow command "config-key"; allow command "osd tree"; allow command "config-key list"; allow command "config-key put"; allow command "config-key get"; allow command "config-key exists"; allow command "osd out"; allow command "osd in"; allow command "osd rm"; allow command "auth del""
# Ask for ceph status:
root@juju-
[errno 2] error connecting to the cluster
# Specify keyring details:
root@juju-
2019-08-15 15:20:43.606 7f0593520700 -1 auth: unable to find a keyring on /var/lib/
2019-08-15 15:20:43.606 7f0593520700 -1 AuthRegistry(
cluster:
id: c6e2d994-
health: HEALTH_WARN
no active mgr
3 monitors have not enabled msgr2
services:
mon: 3 daemons, quorum juju-64b09e-
mgr: no daemons active
osd: 3 osds: 3 up (since 35m), 3 in (since 35m)
data:
pools: 0 pools, 0 pgs
objects: 0 objects, 0 B
usage: 0 B used, 0 B / 0 B avail
pgs:
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ceph 14.2.1-
ProcVersionSign
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CrashDB:
{
}
Date: Thu Aug 15 15:18:58 2019
Ec2AMI: ami-00000734
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.blue
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=screen-
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in cloud-archive: | |
status: | New → Invalid |
Changed in charm-ceph-mon: | |
milestone: | none → 19.10 |
Changed in charm-ceph-mon: | |
status: | Fix Committed → Fix Released |
While the error message the ceph tool prints is a bit confusing the tool still does what it should.
I believe the issue here is a change in the bootstrap process [0] and our charms need to be updated to cope with the new workflow.
The smoking gun is this:
2019-08-19 05:29:00 DEBUG mon-relation- changed /usr/sbin/ ceph-create- keys: This tool is obsolete; mons now create these keys on their own, and changed /usr/sbin/ ceph-create- keys: this tool does nothing except print this message. changed /usr/sbin/ ceph-create- keys: It will be removed in the next release. Please fix your script/tool. to_ceph' 1 more times (delay=15)
2019-08-19 05:29:00 DEBUG mon-relation-
2019-08-19 05:29:00 DEBUG mon-relation-
2019-08-19 05:29:00 INFO juju-log mon:0: Retrying 'add_keyring_
Excerpt from Nautilus release notes [0]:
The ceph-create-keys tool is now obsolete. The monitors automatically create these keys on their own. For now the script prints a warning message and exits, but it will be removed in the next release. Note that ceph-create-keys would also write the admin and bootstrap keys to /etc/ceph and /var/lib/ceph, but this script no longer does that. Any deployment tools that relied on this behavior should instead make use of the ceph auth export <entity-name> command for whichever key(s) they need.
0: https:/ /docs.ceph. com/docs/ master/ releases/ nautilus/