Activity log for bug #1627402

Date Who What changed Old value New value Message
2016-09-25 00:31:14 Chris Hoge bug added bug
2016-10-26 15:07:06 Gregory Haynes diskimage-builder: status New Triaged
2016-10-26 15:07:09 Gregory Haynes diskimage-builder: importance Undecided High
2017-02-28 01:37:38 OpenStack Infra tags in-feature-v2
2017-03-06 00:25:56 OpenStack Infra diskimage-builder: status Triaged In Progress
2017-03-06 00:25:56 OpenStack Infra diskimage-builder: assignee Ian Wienand (iwienand)
2017-04-10 23:29:40 Jimmy McCrory bug added subscriber Jimmy McCrory
2017-04-10 23:31:18 Tom Luong bug added subscriber Tom Luong
2017-04-10 23:31:51 Tom Luong description 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 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
2018-12-03 00:56:09 XiaoRuiguo bug added subscriber XiaoRuiguo