Hardware long gone, invalidate this bug.
** Changed in: maas (Ubuntu)
Status: New => Invalid
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: curtin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
Hello,
sorry that I missed this one,
And yes as Dann mentioned here it was set to boot with PXE first.
I can't check the efibootmgr before / after the grub update as the
hardware has down, I will attach this bug to our trello card to keep it
tracked.
Thanks
--
You received this bug
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To
The system was set to boot from PXE by default, at least before MAAS deployed
it:
Feb 22 03:28:41 lodygin cloud-init[3447]: + echo before grub-install efiboot
settings
Feb 22 03:28:41 lodygin cloud-init[3447]: before grub-install efiboot settings
Feb 22 03:28:41 lodygin cloud-init[3447]: +
Is there any update on this bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To manage notifications about
This is possibly a firmware issue, seeing as the default state for grub
as provided by maas/curtin config should be to skip modifying nvram.
However, how is the system booting in general? Was BootOrder really set
to booting to the network first? If it's set to other devices, and the
other device
Hi, do we have an update on this?
the new SRU cycle has begun and it is blocking us from testing this node.
Or if I should raise this issue to AMD (if it's BIOS/HW related)
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To manage notifications about this bug
Hello,
I'm using MaaS 2.3 (2.3.0-6434-gd354690-0ubuntu1~16.04.1)
For the requested information:
1. curtin config: https://pastebin.canonical.com/p/Ksp7YjYYxB/
2. Installation log for that node: https://pastebin.canonical.com/p/8WKwXxM34V/
3. $ sudo debconf-show debconf
debconf/priority: high
MAAS sends a debconf selection to curtin, so that curtin tells grub to
not update the nvram. The information that's required is:
1. The curtin config sent to curtin (maas machine get-curtin-config
)
2. The installation log (you can grab both the UI/API)
3. The *actual* debconf selection set on
The change in GRUB for bug 1642298 only adds a hook to disable updating
NVRAM - it doesn't change any defaults. The code to do that is in curtin
and/or MAAS. What versions of curtin/MAAS are in use here?
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
12 matches
Mail list logo
