** Changed in: curtin
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
overwri
This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.16
---
grub2 (2.02~beta2-9ubuntu1.16) trusty; urgency=medium
[ Ivan Hu ]
* debian/patches/0001-i386-linux-Add-support-for-ext_lfb_base.patch:
Add support for ext_lfb_base. (LP: #1785033)
[ dann frazier ]
* Add
I think that after such a long time and no movement on the bug, we
should just release this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRA
This bug was fixed in the package grub2-signed - 1.34.18
---
grub2-signed (1.34.18) trusty; urgency=medium
* Rebuild against grub-efi-amd64 2.02~beta2-9ubuntu1.16
(LP: #1785033) (LP: #1642298) (LP: #1696599) (LP: #1792575)
-- Mathieu Trudel-Lapierre Wed, 09 Jan 2019
09:11:55
trusty verification follows. Note: we still haven't gotten to the bottom
of the possible regression in Comment #62, which was correlated with
this same change in xenial. The system where that was seen has been down
for some time, and it is unknown if it is recoverable. I've been unable
to root caus
Hello Rod, or anyone else affected,
Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.16 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (Ubuntu Trusty)
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/1642298
** Changed in: maas/2.2
Status: Triaged => Won't Fix
** Changed in: maas/2.2
Milestone: 2.2.3 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades o
Potential regression found on Xenial, bug 1750732
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
overwritten.
T
This bug was fixed in the package grub2-signed - 1.66.14
---
grub2-signed (1.66.14) xenial; urgency=medium
* Rebuild against grub2 2.02~beta2-36ubuntu3.14. (LP: #1642298)
-- dann frazier Mon, 25 Sep 2017 09:36:55
-0600
** Changed in: grub2-signed (Ubuntu Xenial)
Status:
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.14
---
grub2 (2.02~beta2-36ubuntu3.14) xenial; urgency=medium
* Add grub2/update_nvram template to allow users to disable NVRAM
updates during package upgrades (LP: #1642298).
-- dann frazier Thu, 14 Sep 2017 16:
SRU verification[*]:
ubuntu@dawes:~$ sudo efibootmgr | grep ubuntu
ubuntu@dawes:~$ sudo debconf-show grub-efi-arm64 | grep update_nvram
grub2/update_nvram: true
ubuntu@dawes:~$ sudo dpkg-reconfigure -pcritical grub-efi-arm64
Installing for arm64-efi platform.
Installation finished. No error re
Hello Rod, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.14 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
The uploading purporting to fix this bug is blocked on the verification
of the existing grub2 SRU for bug 1716424.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades
@psusi because the only thing we boot from PXE is a GRUB that chainloads
to the GRUB on disk. We need the GRUB on disk to boot the
kernel/ramdisk/cmdline installed by the OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
So I guess nobody saw my question before. If you are booting with PXE,
then why don't you just not install grub-efi in the first place?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
I found this issue again on Xenial,
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1719271
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM,
Thanks Andres! I've verified that this is working as designed when
deploying zesty. I've prepared an SRU for GRUB in xenial and verified
that it also behaves correctly, so I'll go ahead and upload that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
** Changed in: maas
Milestone: 2.3.0 => 2.3.0alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
overwritt
** Changed in: grub2 (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order
** Changed in: maas
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
o
** Changed in: maas
Status: Confirmed => In Progress
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
Milestone: None => 2.2.3
** Changed in: maas/2.2
Importance: Undecided => High
** Changed in: maas/2.2
Status: New => Triaged
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/330644
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, c
Rod,
I moved my comment to the other bug. But to respond to your comments.
I think your point about #1 is something that should be solved during
installation. There is no reason the Ubuntu installation cannot be smart
enough to re-order the boot order. I think on fresh install that makes
perfect
Blake, your proposal makes sense on the surface; however, there are
cases where it would cause problems. For instance, suppose that, outside
of a MAAS environment, somebody installs Ubuntu, then installs Windows
in a dual-boot configuration, then re-installs Ubuntu because Windows
grabbed the boot
Hi Blake --
Could you please redirect that discussion to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1714090? Which has
been opened to discuss making grub2 UX better on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I think this is more of a GRUB issue overall instead of a MAAS issue
directly. True it affects MAAS and we can do the debconf selections to
work around this issue but overall for quality of Ubuntu I do not
believe this is the proper fix.
I will give an example without MAAS.
1. First the user inst
Ooh, lots of activity while I typed my last comment.
This may be beating a dead horse, but concerning comment #42, Andres, I
tried that command and got similar output:
$ ipmitool -H 10.20.30.13 -I lanplus -U user -P pass chassis bootdev pxe
options=persistent,efiboot
Set Boot Device to pxe
$ ipm
Andres, it's perfectly possible to redeploy a system after it's been set
to boot from the local disk by either adjusting the boot order on the
node or by deleting GRUB from the local disk. I don't recall which of
those I did in the procedure noted in my comment #2, but it was likely
one of those th
30 matches
Mail list logo
