bcache cache_mode setting not configured on servers
Bug #1510334 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| curtin |
Fix Released
|
High
|
Unassigned | ||
Bug Description
MAAS 1.9 alpha.
$ maas env node set-storage-layout $node storage_
Servers are correctly configured using bcache on the root fs, however the cache_mode is writethrough rather than writeback post deployment.
Related branches
lp://staging/~raharper/curtin/set_bcache_cache_mode
- Scott Moser (community): Approve
-
Diff: 104 lines (+44/-1)3 files modifiedcurtin/commands/block_meta.py (+37/-0)
examples/tests/mdadm_bcache.yaml (+1/-0)
tests/vmtests/test_mdadm_bcache.py (+6/-1)
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| importance: | Undecided → High |
| Changed in maas: | |
| status: | New → Triaged |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
| Changed in curtin: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Ryan Harper (raharper) wrote | #2 |
| Changed in curtin: | |
| status: | Triaged → Fix Committed |
| no longer affects: | maas |
Revision history for this message
| Scott Moser (smoser) wrote Fixed in Curtin 17.1 | #3 |
| Changed in curtin: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
MAAS does pass this information to curtin:
- id: bcache0
name: bcache0
type: bcache
backing_device: sda-part3
cache_device: sdb-part1
cache_mode: writethrough <-- passed to curtin
Looking at the curtin code: http://
Curtin is not using that value to set the cache mode for the newly created bcache device.