[SRU] bcache-tools to trusty and precise
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| | curtin |
Medium
|
Unassigned | |||
| | bcache-tools (Ubuntu) |
Wishlist
|
Unassigned | |||
| | Precise |
Wishlist
|
Unassigned | |||
| | Trusty |
Wishlist
|
Unassigned | |||
| cloud-init (Ubuntu) | ||||||
| | Precise |
Undecided
|
Unassigned | |||
| | Trusty |
Undecided
|
Unassigned | |||
Bug Description
[Impact]
bcache-tools is available in vivid, the tools work properly on trusty.
We should have this package in trusty so that we can use the kernel feature.
[Test Case]
On a precise machine install lts-trusty kernel. Setup a bcache partition using the tool.
[Regression Potential]
This is a new package.
Related branches
| Changed in bcache-tools (Ubuntu): | |
| status: | New → Fix Released |
| Robie Basak (racb) wrote : | #1 |
| Changed in bcache-tools (Ubuntu Trusty): | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Blake Rouse (blake-rouse) wrote : | #2 |
We need this in trusty to support deploying Trusty with MAAS using Bcache storage configuration. Please backport bcache-tools.
This should actually be a priority for canonical-server. The support for bcache comes as a priority across all parts of the company and this is part of the features that curtin will support for this cycle.
This was a decision made in Annecy at the mid-cycle sprint!
Thanks
| summary: |
- sru bcache-tools to trusty + [SRU] bcache-tools to trusty |
| Ryan Harper (raharper) wrote : | #4 |
wily has bcache 1.0.8, there are no major changes to bcache itself [1] save fixes for working in systemd pre-boot environments, which for trusty won't matter; there are a number of package fixes[2] related to 1.0.8 intriduction of a bcache_register program introduced for systemd preboot support. I don't see any compelling reason to use 1.0.8 in trusty over what's already in vivid and tested (1.0.7);
1. % git log v1.0.7..v1.0.8
commit a73679b22c33376
Author: Gabriel <email address hidden>
Date: Thu Dec 4 23:44:23 2014 +0100
bcache-
register_quiet doesn't report errors correctly, the following kernel
patch needs to be applied: https:/
See http://
for how this comes up in practice.
Reverts 8327108eeaf3e04
commit 399021549984ad2
Author: Simon Gomizelj <email address hidden>
Date: Sat Jun 28 21:31:51 2014 -0400
Replace bcache-register with c, use builtin kmod
In a pure systemd pre-boot environment, register-bcache can't be shell
code as there is no shell available. Switch to loading the module with
udev's builtin kmod support and introduce a small binary for registering
devices.
Gabriel: Changed errors to be verbose
2. https:/
5. By David Mohr <email address hidden> on 2015-06-11
Only run update-initramfs if installed. Fix dracut. (Closes: #788442)
4. By David Mohr <email address hidden> on 2015-05-26
[ James Page ]
* d/control: Add Vcs fields.
[ David Mohr ]
* Don't depend on initramfs-tools, instead recommend it (Closes: #775674)
* New upstream release 1.0.8
* Update changelog
* Add patch to clean bcache-register
* Update changelog
* Adding dep3 headers to the 0001 patch
* Update watch to use http://
* Add patch for gcc-5 compatability.
Thanks to James Cowgill (Closes: #777798)
| Blake Rouse (blake-rouse) wrote : | #5 |
Now that this is in trusty we also need this in Precise. Without this MAAS will not be able to deploy Precise at all, because of curtin needing bcache-tools.
| Changed in bcache-tools (Ubuntu Trusty): | |
| status: | Triaged → Fix Released |
| summary: |
- [SRU] bcache-tools to trusty + [SRU] bcache-tools to trusty and precise |
| Launchpad Janitor (janitor) wrote : | #6 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in bcache-tools (Ubuntu Precise): | |
| status: | New → Confirmed |
| LaMont Jones (lamont) wrote : | #7 |
bcache-
lamont
Hello Scott, or anyone else affected,
Accepted bcache-tools into precise-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/
| description: | updated |
| Changed in bcache-tools (Ubuntu Precise): | |
| status: | Confirmed → Fix Committed |
| tags: | added: verification-needed |
| Changed in bcache-tools (Ubuntu Precise): | |
| importance: | Undecided → Wishlist |
| Changed in bcache-tools (Ubuntu): | |
| importance: | Undecided → Wishlist |
| LaMont Jones (lamont) wrote : | #9 |
Version 1.0.7-1~12.04.1 works on precise, with the needed (hwe-t) kernel.
| tags: |
added: verification-done removed: verification-needed |
| Launchpad Janitor (janitor) wrote : | #10 |
This bug was fixed in the package bcache-tools - 1.0.7-1~12.04.1
---------------
bcache-tools (1.0.7-1~12.04.1) precise; urgency=medium
* Backport to Precise (LP: #1449099)
-- LaMont Jones <email address hidden> Mon, 09 Nov 2015 14:09:34 -0700
| Changed in bcache-tools (Ubuntu Precise): | |
| status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for bcache-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
| Scott Moser (smoser) wrote : | #12 |
curtin at revno 333 or better has support for bcache on 12.04.
| Changed in curtin: | |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
| no longer affects: | cloud-init (Ubuntu) |
This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New
Thank you.
| Changed in curtin: | |
| status: | Fix Committed → Fix Released |


Not currently a priority for ~canonical-server, but if someone else wants to drive this then that's fine.