@Ryan,
Marking this as invalid for curtin again. I looked closely to the log
and saw this:
May 21 11:00:35 geodude cloud-init[1643]: --2018-05-21 11:00:35--
http://10.244.40.33/MAAS/metadata/latest/by-id/gnbttp/
May 21 11:00:35 geodude cloud-init[1643]: Connecting to 10.244.40.33:80...
On Mon, May 21, 2018 at 3:59 PM, Andres Rodriguez
wrote:
> @Ryan,
>
> I'm marking this as incomplete for curtin provided that after further
> debugging, I can see that the late command that's supposed to send the
> "netboot_off" operation is not being sent.
>
> This could
@Ryan,
I'm marking this as incomplete for curtin provided that after further
debugging, I can see that the late command that's supposed to send the
"netboot_off" operation is not being sent.
This could be because curtin failed but we are lacking logs to determine
this.
** Changed in: curtin
@Ashley,
Could you please start gathering the logs from HAProxy running for the
MAAS servers?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache()
May 21 11:00:42 geodude cloud-init[1643]: curtin: Installation finished.
>From the rsyslog, curtin finished the install without error.
** Changed in: curtin
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thanks for the log. Curtin installed without error, I'll mark invalid.
AFAICT, it booted fine and was instructed to power off.
May 21 13:18:51 geodude cloud-init[1676]: Powering node off.
May 21 13:18:51 geodude ec2:
May 21 13:18:51 geodude ec2:
** Attachment added: "rsyslog-bcache-failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772490/+attachment/5142552/+files/rsyslog-bcache-failure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Attached the rsyslog showing the error. It indeed doesn't seem like
there were any curtin failures, but I wonder that, while curtin
successfully process, the machine actually doesn't actually boot onto
the filesystem due to the kernel issue?
--
You received this bug notification because you are
ay 21 10:57:05 geodude kernel: [ 49.126408] bcache: register_bcache()
error /dev/sda3: device already registered (emitting change event)
These are not curtin or kernel errors but expected output.
I looked at the qa link but I didn't find the install.log debug output.
** Changed in: curtin
Hi Ashley,
Marking this incomplete for MAAS (although I think it is invalid).
Opening a task for curtin and for the kernel team. The error in curtin
implies is the same issue as [1]. Judging from [2], it seems that it
should already be fixed:
May 21 10:57:03 geodude cloud-init[1643]: Processing
** Changed in: maas
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490
Title:
bcache: register_bcache() error
Status in curtin:
New
Status in
11 matches
Mail list logo