canonical / canonical/microceph

After upgrade: `microceph cluster list`: Daemon not yet initialized

Open
#336 1 comment 0 reactions 0 assignees View on GitHub
bug workaround-available
Dominant language
Go
Stars
396
Forks
74
Avg merge
2d 20h
Merged PRs (30d)
7

Description

# Issue report

## What version of MicroCeph are you using ?

```
installed: 0+git.4a608fc (793) 96MB in-cohort,held
```

## What are the steps to reproduce this issue ?

1. Upgrade to 0+git.4a608fc
2. Run `microceph cluster list`

## What happens (observed behaviour) ?

On 2 servers:

```
root@mc11:~# microceph cluster list
Error: Daemon not yet initialized
root@mc12:~# microceph cluster list
Error: Daemon not yet initialized
```

On one different server (cluster of 3), microceph snap would not start at all

```
Error: Unable to start daemon: Daemon failed to start: Failed to initialize trust store: Failed to parse local record "". Found empty certificate
```

## What were you expecting to happen ?

No issue with certificates missing.

## Relevant logs, error output, etc.

If it’s considerably long, please paste to https://gist.github.com/ and insert the link here.

## Additional comments.

I was able to fix it by copying `/var/snap/microceph/common/state/truststore/` from another server. It seems the upgrade removed the truststore (not more yaml find inside).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.