These failures are from a CI job, we always install MAAS just a few minutes
before we hit this failure. At the same time these VMs are having issues
with initrd, other ones are succeeding. It seems really unlikely that it's
a bad image on disk. We can try to reproduce again manually tomorrow and
see though.
Jason
On Thu, Jan 10, 2019 at 7:20 PM Lee Trager <email address hidden> wrote:
> nginx logs are stored in /var/log/maas/http. Looking at your logs it
> seems you images are a few days old. Could you try updating? Once
> updated can you confirm the following SHA256s
>
> e172821ef8bdb36e745b2044f126eb63c89484806a93c2e9790295ac2c8b7944
> /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily/boot-initrd
> 10ab1a486eb79068a52256a375403134200ecf00ded9e24c8da98945b810a2f5
> /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily/boot-kernel
> f6922096bd3e70b18a04b80b1917a0610ee766bc2ca189372e3c4bc072051cd9
> /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily/squashfs
>
> If those check out could you try downloading and reverifying the
> boot-initrd on a remote machine?
> wget
> http://MAAS_IP:5240/images/ubuntu/amd64/generic/bionic/daily/boot-initrd
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810972
>
> Title:
> [2.5] pod VMs fail to commission due to corrupted initrd
>
> Status in MAAS:
> New
>
> Bug description:
> On MaaS HA 2.5, some pod VMs are in 'Ready' state and a few VMs seem
> to get stuck on commissioning.
>
> 2019-01-08-15:12:40 foundationcloudengine.layers.maaslayer INFO Ready:
> 14/19
> Status: {u'landscapeamqp-2': u'Ready', u'landscapeha-1':
> u'Commissioning', u'landscape-1': u'Ready', u'landscapeamqp-1': u'Ready',
> u'juju-1': u'Ready', u'juju-3': u'Ready', u'grafana-1': u'Commissioning',
> u'prometheus-3': u'Ready', u'landscapesql-1': u'Ready', u'landscapesql-2':
> u'Ready', u'juju-2': u'Ready', u'graylog-3': u'Commissioning',
> u'elastic-3': u'Ready', u'elastic-2': u'Ready', u'landscape-3': u'Ready',
> u'landscapeamqp-3': u'Ready', u'thruk-2': u'Commissioning', u'nagios-1':
> u'Commissioning', u'landscape-2': u'Ready'}
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1810972/+subscriptions
>
These failures are from a CI job, we always install MAAS just a few minutes
before we hit this failure. At the same time these VMs are having issues
with initrd, other ones are succeeding. It seems really unlikely that it's
a bad image on disk. We can try to reproduce again manually tomorrow and
see though.
Jason
On Thu, Jan 10, 2019 at 7:20 PM Lee Trager <email address hidden> wrote:
> nginx logs are stored in /var/log/maas/http. Looking at your logs it e745b2044f126eb 63c89484806a93c 2e9790295ac2c8b 7944 maas/boot- resources/ current/ ubuntu/ amd64/generic/ bionic/ daily/boot- initrd 8a52256a3754031 34200ecf00ded9e 24c8da98945b810 a2f5 maas/boot- resources/ current/ ubuntu/ amd64/generic/ bionic/ daily/boot- kernel 18a04b80b1917a0 610ee766bc2ca18 9372e3c4bc07205 1cd9 maas/boot- resources/ current/ ubuntu/ amd64/generic/ bionic/ daily/squashfs MAAS_IP: 5240/images/ ubuntu/ amd64/generic/ bionic/ daily/boot- initrd /bugs.launchpad .net/bugs/ 1810972 engine. layers. maaslayer INFO Ready: p-2': u'Ready', u'landscapeha-1': /bugs.launchpad .net/maas/ +bug/1810972/ +subscriptions
> seems you images are a few days old. Could you try updating? Once
> updated can you confirm the following SHA256s
>
> e172821ef8bdb36
> /var/lib/
> 10ab1a486eb7906
> /var/lib/
> f6922096bd3e70b
> /var/lib/
>
> If those check out could you try downloading and reverifying the
> boot-initrd on a remote machine?
> wget
> http://
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [2.5] pod VMs fail to commission due to corrupted initrd
>
> Status in MAAS:
> New
>
> Bug description:
> On MaaS HA 2.5, some pod VMs are in 'Ready' state and a few VMs seem
> to get stuck on commissioning.
>
> 2019-01-08-15:12:40 foundationcloud
> 14/19
> Status: {u'landscapeamq
> u'Commissioning', u'landscape-1': u'Ready', u'landscapeamqp-1': u'Ready',
> u'juju-1': u'Ready', u'juju-3': u'Ready', u'grafana-1': u'Commissioning',
> u'prometheus-3': u'Ready', u'landscapesql-1': u'Ready', u'landscapesql-2':
> u'Ready', u'juju-2': u'Ready', u'graylog-3': u'Commissioning',
> u'elastic-3': u'Ready', u'elastic-2': u'Ready', u'landscape-3': u'Ready',
> u'landscapeamqp-3': u'Ready', u'thruk-2': u'Commissioning', u'nagios-1':
> u'Commissioning', u'landscape-2': u'Ready'}
>
> To manage notifications about this bug go to:
> https:/
>