On Wed, Aug 29, 2018 at 9:40 AM Rod Smith <email address hidden> wrote:
>
> I assume you mean the /root/curtin-install.log file, which I'm
> attaching. If you mean another file, please clarify.
That's the file; however debugging output is not enabled. Could you
enable that and get the install log?
Before the install if you could attach efibootmgr -v output with the
loader paths
I'll take that and look at the code which reorders boot entries and see if
we can sort out if it's a curtin bug.
That code for resorting hasn't changed since 2017-05-11
On Wed, Aug 29, 2018 at 9:40 AM Rod Smith <email address hidden> wrote: install. log file, which I'm
>
> I assume you mean the /root/curtin-
> attaching. If you mean another file, please clarify.
That's the file; however debugging output is not enabled. Could you
enable that and get the install log?
maas <user> maas set-config name=curtin_verbose value=True
Before the install if you could attach efibootmgr -v output with the
loader paths
I'll take that and look at the code which reorders boot entries and see if
we can sort out if it's a curtin bug.
That code for resorting hasn't changed since 2017-05-11
https:/ /git.launchpad. net/curtin/ tree/curtin/ commands/ curthooks. py#n219
> curtin- install. log file from one affected server (jolteon)" /bugs.launchpad .net/curtin/ +bug/1789650/ +attachment/ 5182207/ +files/ curtin- install. log /bugs.launchpad .net/bugs/ 1789650 /bugs.launchpad .net/curtin/ +bug/1789650/ +subscriptions
> ** Attachment added: "/root/
> https:/
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https:/
>
> Title:
> Servers set to boot from disk after MAAS installation
>
> To manage notifications about this bug go to:
> https:/