On Fri, Jun 10, 2016 at 5:49 PM, Mike Pontillo <email address hidden>
wrote:
> I was in the middle of doing a packet capture to try to troubleshoot the
> issue before Andres determined it was "Invalid" for MAAS.
>
> Here's a packet capture that shows Curtin's last words on the network,
> in case it helps:
>
> https://paste.ubuntu.com/17190232/
>
> This was with curtin bzr389.
>
I don't understand. The trace clearly shows curtin posting events in
detail back to maas.
Why aren't these shown?
Do we have a trace from the previous curtin which succeeds?
I do know that curtin now sends
level: "INFO"
in the data. where prior versions didn't include the level key.
I just don't see how if curtin is posting this too maas and what appears
from the trace is that maas is *getting* the data, the even, how this is a
curtin issue?
On Fri, Jun 10, 2016 at 5:49 PM, Mike Pontillo <email address hidden>
wrote:
> I was in the middle of doing a packet capture to try to troubleshoot the /paste. ubuntu. com/17190232/
> issue before Andres determined it was "Invalid" for MAAS.
>
> Here's a packet capture that shows Curtin's last words on the network,
> in case it helps:
>
> https:/
>
> This was with curtin bzr389.
>
I don't understand. The trace clearly shows curtin posting events in
detail back to maas.
Why aren't these shown?
Do we have a trace from the previous curtin which succeeds?
I do know that curtin now sends
level: "INFO"
in the data. where prior versions didn't include the level key.
I just don't see how if curtin is posting this too maas and what appears
from the trace is that maas is *getting* the data, the even, how this is a
curtin issue?