Thank for the log. If it's reproducible, can you re-run the deployment
with curtin verbosity set ?
And can you attach the configuration that you're deploying? I'm especially
interested in the number of bcache backing devices and how many cache
devices.
Thank for the log. If it's reproducible, can you re-run the deployment
with curtin verbosity set ?
And can you attach the configuration that you're deploying? I'm especially
interested in the number of bcache backing devices and how many cache
devices.
% maas {profile} maas set-config name=curtin_verbose value=true
https:/ /discourse. maas.io/ t/getting- curtin- debug-logs/ 169
On Fri, Dec 14, 2018 at 5:01 PM Pedro Guimarães <email address hidden>
wrote:
> ** Tags added: cpe-onsite /bugs.launchpad .net/bugs/ 1796292 /bugs.launchpad .net/curtin/ +bug/1796292/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https:/
>
> Title:
> Tight timeout for bcache removal causes spurious failures
>
> To manage notifications about this bug go to:
> https:/
>