When I attempt to perform the quick-wipe on disks that have been configured
in bcache mode
that operation fails. I'm interested in if you're also seeing this.
>
> -> second deployment with the same configuration fails with:
> An error occured handling 'vda-part2': OSError - [Errno 16] Device or
> resource busy: '/dev/vda2'
>
Do you have the entire log here? In the early part of the curtin install
process, curtin dumps
the block device tree layout w.r.t which devices has a holder (like
bcache). I'd like to see what curtin
saw on this second run.
On Fri, Oct 13, 2017 at 1:34 PM, Nobuto Murata <email address hidden>
wrote:
> How to reproduce:
>
> $ maas admin machine deploy retc7f
> $ maas admin machine get-curtin-config retc7f > curtin-config.yaml
>
> -> first deployment succeeds
>
> $ maas admin machine release retc7f erase=true quick_erase=true
> -> quick erase succeeds
>
Do you have the log for this operation?
When I attempt to perform the quick-wipe on disks that have been configured
in bcache mode
that operation fails. I'm interested in if you're also seeing this.
> config_ after_erase. yaml
> $ maas admin machine deploy retc7f
> $ maas admin machine get-curtin-config retc7f >
> curtin-
>
There is no change in config (which is good).
>
> -> second deployment with the same configuration fails with:
> An error occured handling 'vda-part2': OSError - [Errno 16] Device or
> resource busy: '/dev/vda2'
>
Do you have the entire log here? In the early part of the curtin install
process, curtin dumps
the block device tree layout w.r.t which devices has a holder (like
bcache). I'd like to see what curtin
saw on this second run.
> -- /bugs.launchpad .net/bugs/ 1718699 /bugs.launchpad .net/curtin/ +bug/1718699/ +subscriptions
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> curtin fails to setup bcache when unclean bcache from previous install
> exists
>
> To manage notifications about this bug go to:
> https:/
>