@Jason, On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs wrote: > On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez > 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. > The tftp issue shows no evidence this is causing any booting failures. We have seen this issue before and confirmed that it doesn't cause boot issues. See [1]. If you want to try it, it is available in ppa:maas/proposed. [1].https://bugs.launchpad.net/maas/+bug/1376483 As far as the postgresql logs with "maas@maasdb ERROR: could not serialize access due to concurrent update" that is *not* a bug in MAAS or an issue. That's perfectly normal messages with the isolation level the MAAS DB is running with. This basically means something else is trying to update the db while something else is updating it, and MAAS already handles this by doing retries. > > 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. > CPU load is not CPU utilization. We know that at the time there's 6 other VM's with 150%+ CPU usage are writing to the disk because they are being deployed and/or configured (e.g. software installation). Correct me if wrong, but this can cause the prioritization of whatever is writing to disk over anything else, like the MAAS processes access for resources. That being said, because CPU load doesn't show high we are making the *assumption* that it is not impacting MAAS, but again, this is an assumption. Making the requested change for having at least 4 CPUs (ideally 6) would allow us to determining what are the effects and see whether there's any difference on behavior and would help identify what other issues. Without having the comparison then we are making it more difficult to isolate the problem. > > Jason > > > ** Changed in: maas > Status: Incomplete => New > > -- > You received this bug notification because you are subscribed to MAAS. > 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 > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=maas; milestone=2.4.x; status=New; > importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main; > status=In Progress; importance=Medium;