Comment 13 for bug 1514094

Hi Blake,
as discussed on IRC it was meant to fail to provide more insight via better debugging info.
I think I found the root cause of your last reported bug. It only triggered on older kernel bcache implementations which was why it was harder to spot at first.

I tested the new code on vivid/wily.
I also was able to extend the vmtest to trusty (still shaky). I might hit non related issues with that.
(extending coverage to various release/hwe combinations is an ongoing effort of the last weeks, but often has to be postponed for other more urgent things).

Therefore I need you for the MAAS/Trusty environment that you are running in.
Starting with version 325 in branch lp:~paelzer/curtin/fix-1514094-v1 the fix is in.

The former issue you had should be fixed, please test it and let me know the results in your environment.
If you are running in any of these issues it is "good" as those are the ones I currently can recreate:
 * bcache: __cached_dev_store() Can't attach a49890b1-2103-4e2e-a47d-cc56558e8f7d: cache set not found
 * Stderr: u'Already a bcache device on /dev/vdb6, overwrite with --wipe-bcache\n'
 * An error occured handling 'bcache_normal': ValueError - Invalid number of holding devices: []