jujud services not starting after reboot when /var is on separate partition
Bug #1634390 reported by
Sandor Zeestraten
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Vinodhini | ||
juju-core |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
# Issue
We have machines in MAAS where we've split /var to a separate partition.
Deploying machines and services with Juju works fine, however the juju agent (jujud) services will not start when a machine restarts as systemd does not find the services on start due to (I believe) them being symlinked from /var/lib/juju/init/
As a workaround, you can reload systemd so it finds the services and then manually enable them, however that is not a proper solution.
# Output from df and systemctl
http://
# Versions
Juju 2.0.0-xenial-amd64
MAAS 2.0.0
Changed in juju: | |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → 2.1.0 |
Changed in juju: | |
importance: | Medium → Critical |
Changed in juju: | |
milestone: | 2.1.0 → 2.2.0 |
importance: | Critical → High |
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 1.25.10 |
Changed in juju-core: | |
milestone: | 1.25.10 → none |
Changed in juju-core: | |
milestone: | none → 1.25.11 |
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju-core: | |
milestone: | 1.25.11 → none |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
milestone: | none → 2.4-beta1 |
importance: | Medium → High |
Changed in juju: | |
assignee: | nobody → Vinodhini (vinu-b) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.4-beta1 → none |
Changed in juju: | |
milestone: | none → 2.4-beta2 |
Changed in juju: | |
milestone: | 2.4-beta2 → none |
Changed in juju: | |
milestone: | none → 2.4-rc1 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I managed to reproduce the issue in a fresh MAAS setup.
Deployed two different machines, one with just / and one with split partition / and /var
# Works OK maas-node06: ~$ sudo lsblk -o NAME,FSTYPE, SIZE,MOUNTPOINT ,LABEL
ubuntu@
NAME FSTYPE SIZE MOUNTPOINT LABEL
vda 20G
└─vda1 LVM2_member 20G
└─vgroot-root ext4 9.3G /
vdb 10G
# Does not work maas-node07: ~$ sudo lsblk -o NAME,FSTYPE, SIZE,MOUNTPOINT ,LABEL
ubuntu@
NAME FSTYPE SIZE MOUNTPOINT LABEL
vda 20G
└─vda1 LVM2_member 20G
├─vgroot-root ext4 9.3G /
└─vgroot-var ext4 4.7G /var
vdb 10G