Comment 19 for bug 1590846

On Sat, Jun 11, 2016 at 12:13 PM, Andres Rodriguez <email address hidden>
wrote:

> Hi Ryan,
>
> Let me explain this better:
>
> When I use MAAS 2.0 with curtin 0.1.0~bzr365-0ubuntu1 installed, the
> following happens:
>
> 1. I deploy a machine
> 2. MAAS receives status messages from both, curtin/clout-init.
> 3. The machine installs successfully.
> 4. After the install, install.log is stored.
> 5. Full list of events/status messages:
> http://pastebin.ubuntu.com/17218366/
> 6. Logs on regiond.log (ignore the difference on the date here, because
> logs time is UTC): http://paste.ubuntu.com/17218488/
>
> Now, if I use the /same/ MAAS with curtin 0.1.0~bzr389-0ubuntu1~16.04.1,
> the following happens:
>
> 1. I deploy a machine
> 2. MAAS receives status messages from both, curtin/cloud-init
> 3. The machine installs successfully.
> 4. After the install, install.log is NOT stored.
> - Full list of events/status messages:
> http://pastebin.ubuntu.com/17219039/
> - Logs on regiond.log: http://paste.ubuntu.com/17218981/
>
> While I have not done a packet capture like Mike has, I do see that
> Mike's packet capture correctly reflects what's currently happening.
> Curtin is sending status messages/events, which are correctly stored,
> *however* it does not seem to be sending 'install.log' at all. So this
> is definitely a regression in curtin's side. The simple fact that with
> curtin 0.1.0~bzr365-0ubuntu1 install.log is stored, and with curtin
> 0.1.0~bzr389-0ubuntu1~16.04.1 install.log is not stored, confirms this.
>

Thanks for the clarification. That helps me focus on the test-case needed
here, the post_files portion.

I'll setup a test-case and see where we go from there.