Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 7 August 2014 03:13, William Reade wrote: > SGTM too. It should always have worked like this -- rerunning all our > upgrade steps every time is *crazy*. > > Sorry, I got this detail wrong. The machine agent isn't rerunning upgrade steps unnecessarily, but it is waiting for an unnecessarily lon

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 6 August 2014 19:09, Dimiter Naydenov wrote: > > 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 upgra

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 6 August 2014 18:32, John Meinel wrote: > That sounds like what I would have expected was happening (we only run > upgrade steps if we think they have a reason to change things, and then > only set the last known version once all the upgrade steps have finished.) > > I'm concerned about the "

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-06 Thread William Reade
SGTM too. It should always have worked like this -- rerunning all our upgrade steps every time is *crazy*. On Wed, Aug 6, 2014 at 3:19 AM, David Cheney wrote: > SGTM. > > On Wed, Aug 6, 2014 at 11:10 AM, Menno Smits > wrote: > > Right now, a Juju machine agent is in "upgrade mode" from the mom

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-06 Thread Dimiter Naydenov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This SGTM as well, however (see below)... On 6.08.2014 04:10, Menno Smits 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 heavi

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-06 Thread Dimiter Naydenov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This SGTM as well, however (see below)... On 6.08.2014 04:10, Menno Smits wrote: If you are referring to Upgraded-To version field in agent config, I think this is set after the upgrade completes, so it might be unavailable before that. - -- Di

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-05 Thread John Meinel
That sounds like what I would have expected was happening (we only run upgrade steps if we think they have a reason to change things, and then only set the last known version once all the upgrade steps have finished.) I'm concerned about the "if there is a mongo problem", because if we're running

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-05 Thread Horacio Duran
You had my verbal SGTM but have it written also On Tuesday, August 5, 2014, David Cheney wrote: > SGTM. > > On Wed, Aug 6, 2014 at 11:10 AM, Menno Smits > wrote: > > Right now, a Juju machine agent is in "upgrade mode" from the moment it > > starts until the upgrade-steps worker is finished. Du

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-05 Thread David Cheney
SGTM. On Wed, Aug 6, 2014 at 11:10 AM, Menno Smits 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 upgra

avoiding unnecessarily entering "upgrade mode"

2014-08-05 Thread Menno Smits
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 perfor