bcache mounts inconsistent after node reboots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Charm Test Infra |
Fix Released
|
Undecided
|
Unassigned | ||
curtin |
Fix Released
|
High
|
Unassigned |
Bug Description
On MAAS-deployed nodes with bcache-fronted disks, the bcache device names and mount points can move about after reboots, causing systems to not boot, and/or cause system outage and/or risk of data loss.
Perhaps a disk ID or label should be used to ensure the intended device is brought up on the intended mount point?
ubuntu@
# The following two lines are the original values as-deployed by maas
#/dev/bcache1 / ext4 defaults 0 0
#/dev/bcache0 /srv ext4 defaults 0 0
#
# After a reboot, the root and srv partitions inverted. I had to edit
# fstab for things to work again. The following two lines became necessary:
/dev/bcache0 / ext4 defaults 0 0
/dev/bcache1 /srv ext4 defaults 0 0
#
UUID=3793a969-
UUID=186E-7F1F /boot/efi vfat defaults 0 0
/swap.img none swap sw 0 0
Related branches
- Scott Moser (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 156 lines (+32/-44)2 files modifiedcurtin/commands/block_meta.py (+5/-9)
tests/vmtests/test_basic.py (+27/-35)
tags: | added: canonical-bootstack cpec |
tags: |
added: cpe-onsite removed: cpec |
Changed in charm-test-infra: | |
status: | Confirmed → Fix Released |
Hi Bryan,
Since it is curtin the one that writes out the storage configuration, I believe this is a curtin related issue. As such, opening a curtin task for this. That said, could you please provide the following:
1. What's the MAAS and Curtin version?
dpkg -l | grep maas
dpkg -l | grep curtin
2. Get the storage config:
maas <user> machine get-curtin-config <system_ id_of_machine>