** No longer affects: shim-signed (Ubuntu)
** Summary changed:
- shim-signed fails to install if grub disk config is incorrect
+ GRUB (re)installation failing due to stale grub-{pc,efi}/install_devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config is inco
This should really be fixed properly and officially.
It's an issue in the default Azure image and in the way Azure deploys a
VM with a bigger root disk size than the image and therefore it should
be looked into by whoever is in charge of supporting Ubuntu on Azure.
--
You received this bug notif
We "solved" it by reinstalling grub.
I.e.
export DEBIAN_FRONTEND=noninteractive
apt-get purge grub\* -y --allow-remove-essential
apt-get install grub-efi -y
apt-get autoremove -y
update-grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
We seem to be hitting the same issue, also on Azure.
It happens when we deploy a VM from a Shared Image gallery and change
the OS disk size during deployment. We use a template spec to deploy the
VM. If we set diskSizeGB in the storageProfile, the issue appears.
mount: /var/lib/grub/esp: special
More context:
cat /boot/grub/device.map
cat: /boot/grub/device.map: No such file or directory
sudo debconf-show grub-pc | grep grub-pc/install_devices
grub-pc/install_devices_failed: false
grub-pc/install_devices_failed_upgrade: true
* grub-pc/install_devices_empty: false
grub-pc/install_de
No
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config is incorrect
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Did you remove or reconfigure any data disks before this bug appeared?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config is incorrect
To
We are using the "rest" api. Storage profiles look something like:
{
"imageReference": {
"publisher": "canonical",
"offer": "0001-com-ubuntu-server-focal",
"sku": "20_04-lts",
"version": "latest"
},
"osDisk": {
"name": "yadayada-os",
"managedDisk": {
"storageAc
Are you using packer or anything else to modify the image? How are you
modifying the disk layout?
I'll double check against some of the provided VM sizes, but I don't
think this is a problem with the image. It's likely a configuration
issue...which is *not* to say it's not a bug.
--
You received
Great!
Standard_B1ms
Standard_B1s
Standard_D16as_v4
Standard_D2as_v4
Standard_D8as_v4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config i
Hi @abaelter, I'm from the Canonical Public Cloud team. I'll be looking
into this further.
Can you tell me what Azure VM size(s) you've observed this occurring on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
We are only seeing it on Azure, but other cloud providers Ubuntu images
don't come with shim-signed so that's why I though we could remove it.
lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:00 55.5M 1 loop /snap/core18/2074
loop2 7:20 32.3M 1 loop /snap/snapd/12398
do you mind providing your grub configuration? (I know you said it was
system default in the other bug), but I'd like to compare it against our
fresh VM boot just to see if anything was awry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have been looking into why this has been happening on Azure Ubuntu
VMs, but I have not been able to reproduce:
I'm running:
az vm create --name bug-test --resource-group canonical-patviafore
--location southcentralus --image Canonical:0001-com-ubuntu-server-
focal:20_04-lts:20.04.202107200 --s
It's not specific to Azure VMs, it's a problem whenever the disk
configuration has changed vs what it was when grub was installed. It's
unclear why this is happening for you in Azure; I defer to Pat from our
Certified Public Cloud team who was investigating this.
--
You received this bug notific
Ok, seemed like some Microsoft thing I don't need. But ok, to bad I have
to do that on ~500 vms.
How come this is only an issue on Azure Ubuntu vms?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19407
> Is it safe to remove shim-signed?
Certainly not. And it wouldn't fix the problem of grub-multi-install
failing.
You can run dpkg-reconfigure grub-pc manually, which should allow you to
update the disk configuration.
--
You received this bug notification because you are a member of Ubuntu
Bug
Is it safe to remove shim-signed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config is incorrect
To manage notifications about this bug g
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim
looking at the dpkg history it appears update-manager/aptdaemon was
installing the package, so this isn't a problem of a non-interactive
upgrade with no debconf frontend available (and if it were, that should
result in an exit code of 1, not 32).
So there appears to be a bug in /usr/lib/grub/grub-
Please show the output of 'debconf-show grub-pc|grep install'.
** Summary changed:
- package shim-signed 1.40.6+15.4-0ubuntu7 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
status 32
+ shim-signed fails to install if grub disk c
23 matches
Mail list logo
