** 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/1743249
Title:
High IO on the system prevents MAAS to provide PXE config in a timely
** Changed in: maas
Milestone: 2.4.x => 2.4.0beta1
--
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:
High IO on the system prevents MAAS to provide PXE config in a timely
manner
** Merge proposal linked:
https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/341132
--
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:
High IO on the system prevents MAAS to
Infosys asking us to rename any kvm to their data center standard. This
patch is a concerned to do that.
--
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:
High IO on the system prevents
** Changed in: maas
Status: Triaged => 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/1743249
Title:
High IO on the system prevents MAAS to provide PXE config in a timely
** Merge proposal linked:
https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/337233
--
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:
High IO on the system prevents MAAS to
And summarizing the changes we've put in place here.
1. We started doing our juju bootstrap --to a VM on a node which isn't
the PostgreSQL master. This didn't stop the problem from occurring
frequently.
2. We have a bcache on /var in write-back mode. This seems to have made
the issue stop
Ok - I filed a few more bugs to cover the aspects of this failure other
than the slow response for grub.cfg.
bug 1747927 - grub should not hang waiting for user input when booting
from MAAS.
bug 1747928 - When a known server in Deploying state boots to the
enlisting environment, it should not
Andres, there is more to this bug than just the slow grub response.
MAAS could do more after the fact to recover in this situation. For
example, once a machine boots to the ephemeral environment, it has
plenty of time to talk to MAAS and find out it's not actually supposed
to be enlisting, and
