You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
minio role: systemd unit stays 'inactive' after install #9
Deployed a VM with the minio service role attached (default/empty config
no volume_path/console_port/root_user override submitted), on the
Ubuntu 24.x "with PlusClouds Service" image. After SSH login succeeded, systemctl is-active minio reported inactive (never started, as
opposed to crashing into failed) for the full 300s verification window,
and /minio/health/live on :9000 was unreachable (curl couldn't connect
at all - exit 7).
Repro
POST /leo/iaas/virtual-machines/create-wizard with service_roles: {"minio": {"config": {}}} against the Ubuntu 24.x "with
PlusClouds Service" image, then after boot:
inactive (rather than failed) suggests the unit may simply never have
been started/enabled, rather than crashing on start - possibly a missed systemctl enable --now step in the install script. The VM was deployed
and torn down automatically as part of the test run, so the live
VM/journalctl -u minio output is gone - filed from the test's captured
output, not a live inspection.
Found via leo4.tester's iaas-service-roles automated test scenario.
Fixed in v1.6.3 (fa0b3be). Root cause: neither the .deb nor the .rpm MinIO package creates the minio-user system account it needs — that's a manual step in MinIO's own install docs, not something the package postinst handles. capabilities/service-roles/minio/linux.yml referenced owner: minio-user/group: minio-user for the data directory and /etc/default/minio without ever creating that account, so the role failed outright on a fresh install (unknown user), and the enable/start step was never reached — matching the reported inactive state. Added explicit group/user creation tasks before they're referenced.
Verified by cross-checking MinIO's own systemd deployment docs (which list groupadd/useradd for minio-user as a required manual step) and confirming the role had no equivalent task, unlike every other role in this repo that creates its own system user.
Activity
fix: repair minio, prometheus, and jenkins service-role installs
yakari007 commentedon Aug 3, 2026
Fixed in v1.6.3 (fa0b3be). Root cause: neither the
.debnor the.rpmMinIO package creates theminio-usersystem account it needs — that's a manual step in MinIO's own install docs, not something the package postinst handles.capabilities/service-roles/minio/linux.ymlreferencedowner: minio-user/group: minio-userfor the data directory and/etc/default/miniowithout ever creating that account, so the role failed outright on a fresh install (unknown user), and the enable/start step was never reached — matching the reportedinactivestate. Added explicit group/user creation tasks before they're referenced.Verified by cross-checking MinIO's own systemd deployment docs (which list
groupadd/useraddforminio-useras a required manual step) and confirming the role had no equivalent task, unlike every other role in this repo that creates its own system user.