On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
<[email protected]> wrote:
> No new data was provided to mark this New in MAAS:
>
> 1. Changes to the storage seem to have improved things
Yes, it has. That doesn't change whether or not there is a bug in
MAAS. Can you please address the critical log errors that I mentioned
in comment #36? This seems like enough to establish something is
going wrong in MAAS.
> 2. No tests have been run with fixed grub that have caused boot
failures.
The comments from #56 were testing with the fixed grub - sorry if that
wasn't clear.
> 3. AFAIK, the VM config has not changed to use less CPU to compare
results and whether this config change causes the bugs in question.
The CPU load data from comments #48 and #50 shows that CPU load is not
the problem. The max load average was under 12 on a 20 thread system.
That means there was lots of free CPU time, and that this workload is
not CPU bound.
Jason
** Changed in: maas
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/1743249
Title:
Failed Deployment after timeout trying to retrieve grub cfg
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
