Comment 2 for bug 1520400

lvmmetad is not fatal, but this appears to be:

[ 112.498505] cloud-init[1139]: /dev/vgroot/lvroot: not found: device
not cleared
[ 112.499834] cloud-init[1139]: Aborting. Failed to wipe start of new LV.
[ 116.534735] cloud-init[1139]: An error occured handling
'vgroot-lvroot': ProcessExecutionError - Unexpected error while
running command.

Would be good to see the storage config passed to curtin and a clean
run with the current "fixes" (fp vs fp.read() and flash-kernel)
applied to see what the current error looks like.

On Fri, Dec 4, 2015 at 9:12 AM, Scott Moser <email address hidden> wrote:

> The second paste http://paste.ubuntu.com/13522047/ seems to show the
> primary failure is:
> [ 111.718754] cloud-init[1139]: /run/lvm/lvmetad.socket: connect failed:
> No such file or directory
> [ 111.730177] cloud-init[1139]: WARNING: Failed to connect to lvmetad.
> Falling back to internal scanning.
>
>
> It would seem that something caused lvm to not correctly start on
> installation.
> Could you please get a failure like that and provide the full log?
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1520400
>
> Title:
> curtin error on arm64 wily deployment for xgene-2 Soc
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1520400/+subscriptions
>