Comment 0 for bug 1627402

Revision history for this message
Chris Hoge (hoge) wrote :

Building, on xenial, a baremetal ubuntu xenial image for baremetal with grub2 fails.

Command line and output here:
http://paste.openstack.org/show/582870/

DIB_DEV_USER_USERNAME=******** DIB_DEV_USER_SHELL=/bin/bash DIB_DEV_USER_PWDLESS_SUDO=true DIB_DEV_USER_AUTHORIZED_KEYS=******** DIB_DEV_USER_PASSWORD=******** DIB_RELEASE=xenial disk-image-create ubuntu grub2 baremetal devuser

Creating config file /etc/default/grub with new version
Generating grub configuration file ...
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Found linux image: /boot/vmlinuz-4.4.0-38-generic
Found initrd image: /boot/initrd.img-4.4.0-38-generic
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
done
Setting up grub-efi-amd64-signed (1.66.2+2.02~beta2-36ubuntu3.2) ...
Processing triggers for shim-signed (1.18~16.04.1+0.8-0ubuntu2) ...
No DKMS packages installed: not changing Secure Boot validation state.
+ dpkg --configure grub-efi-amd64
dpkg: error processing package grub-efi-amd64 (--configure):
 package grub-efi-amd64 is already installed and configured
Errors were encountered while processing:
 grub-efi-amd64