After update to the latest curtin that changes the log to install.log MAAS show's two installation logs

I think this is a trivial case of reverting Newell's patch that fixed up the original log name. Newell?

Andreas,

The Installation output reports will show *all* the latest reports for a given node. Since the file name has changed this is in effect *a different report*. I assume you used the same node and that is why you are getting both installation reports; one for the previous version of curtin you had installed, and the other for the newest curtin version you installed.

s/Andreas/Andres... my apologies!

While the name of the log might have changed, MAAS needs to know how to
handle that... not because the log name changes in curtin, MAAS will
believe it is a different log and just start appending or adding more logs.
MAAS should replace that automatically.

On Mon, Oct 27, 2014 at 8:36 PM, Newell Jensen <email address hidden>
wrote:

> Andreas,
>
> The Installation output reports will show *all* the latest reports for a
> given node. Since the file name has changed this is in effect *a
> different report*. I assume you used the same node and that is why you
> are getting both installation reports; one for the previous version of
> curtin you had installed, and the other for the newest curtin version
> you installed.
>
> ** Changed in: maas
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1386432
>
> Title:
> After update to the latest curtin that changes the log to install.log
> MAAS show's two installation logs
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1386432/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Does this only affect people that upgraded from a previous version of MAAS/curtin within 1.7 to the latest MAAS/curtin 1.7?

This will only affect people that had a previous version of MAAS (starting
in 1.7) and then upgraded curtin, yes.

After some thought and talking to others, it is probably best that when we
"Release" or "Mark Fixed" a node, that we should delete the installation
results for a node. The reason for putting that in "Mark Fixed" instead of
"Mark Broken" is because they might want to see the installation output
results while debugging. I am currently working on a patch for this.

On Tue, Oct 28, 2014 at 12:21 PM, Christian Reis <email address hidden> wrote:

> Does this only affect people that upgraded from a previous version of
> MAAS/curtin within 1.7 to the latest MAAS/curtin 1.7?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1386432
>
> Title:
> After update to the latest curtin that changes the log to install.log
> MAAS show's two installation logs
>
> Status in MAAS:
> Triaged
>
> Bug description:
> An older curtin version created the installation log as
> curtin_install.log. This made it show up in the UI as Curtin Install
> Log.
>
> Curtin, in trunk, changed this to install.log. This correctly shows in
> the WebUI. However, MAAS now shows 2 logs:
>
> Installation output
> install log curtin install log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1386432/+subscriptions
>

Punting to next as this isn't really critical.