canonical / canonical/microceph

Error: failed to add loop OSD: failed to start osd.2: Failed to run: snapctl restart --reload microceph.osd: exit status 1

Open
#603 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
396
Forks
74
Avg merge
2d 20h
Merged PRs (30d)
7

Description

```
$ sudo microceph disk add loop,2G,3

+-----------+---------+
| PATH | STATUS |
+-----------+---------+
| loop,2G,3 | Failure |
+-----------+---------+
Error: failed to add loop OSD: failed to start osd.4: Failed to run: snapctl restart --reload microceph.osd: exit status 1 (error: snapctl: cannot perform the following tasks:
- Run service command "reload-or-restart" for services ["osd"] of snap "microceph" (systemctl command [reload-or-restart snap.microceph.osd.service] failed with exit status 1: stderr:
Job for snap.microceph.osd.service failed because the control process exited with error code.
See "systemctl status snap.microceph.osd.service" and "journalctl -xeu snap.microceph.osd.service" for details.))
```

Logs:

[journald.log](https://github.com/user-attachments/files/21711451/journald.log)

[logs.zip](https://github.com/user-attachments/files/21711453/logs.zip)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with `sudo microceph disk add loop,2G,3`, then inspect journald.log and logs.zip alongside the reported `systemctl status` and `journalctl -xeu` commands. Done means identifying why the microceph OSD service fails to reload or restart and confirming that adding the loop-backed disk completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.