<div dir="ltr">SGTM too. It should always have worked like this -- rerunning all our upgrade steps every time is *crazy*.</div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Aug 6, 2014 at 3:19 AM, David Cheney <<a href="mailto:david.cheney@canonical.com" target="_blank">david.cheney@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">SGTM. <div class="HOEnZb"><div class="h5"> On Wed, Aug 6, 2014 at 11:10 AM, Menno Smits <<a href="mailto:menno.smits@canonical.com">menno.smits@canonical.com</a>> wrote: > Right now, a Juju machine agent is in "upgrade mode" from the moment it > starts until the upgrade-steps worker is finished. During this period API > logins are heavily restricted and most of the agent's workers don't start > until upgrade mode stops. > > This happens even when there is no upgrade to perform. The upgrade-steps > worker always runs at machine agent startup and upgrade mode is in force > until it finishes. > > Upgrade mode is typically short-lived (say 10 seconds) but if something is > wrong (e.g. mongo issues) the upgrade-steps worker may take longer or not > finish resulting in the user seeing lots of "upgrade in progress" messages > from the client and in the logs. > This is particularly confusing when a user hasn't even requested an upgrade > themselves. > > I would like to change the machine agent so that upgrade mode is only > entered if the version in agent.conf is different from the running software > version. This would mean that upgrade mode is only entered if there is an > actual upgrade to perform. > > The version in agent.conf is only updated after a successful upgrade so it > is the right thing to use to determine if upgrade mode should be entered. > > The current behaviour means that the (idempotent) upgrade steps for the > current version are always run each time the machine agent starts. If the > change I'm proposing is implemented this will no longer happen. Does this > seem like a problem to anyone? For instance, do we rely on the upgrade steps > for the current version being run after bootstrap? > > The ticket for this work is at: <a href="https://bugs.launchpad.net/bugs/1350111" target="_blank">https://bugs.launchpad.net/bugs/1350111</a> > > Cheers, > Menno > > > </div></div>> -- > Juju-dev mailing list > <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a> > Modify settings or unsubscribe at: > <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a> > -- Juju-dev mailing list <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a> </blockquote></div> </div>