Increment juju stable 1.20 to 1.20.0
state.address.NetworkScope was renamed to
Scope, with no explicit bson field name
specified. This is a schema change, and
broke upgrade from 1.18 to 1.19.

Fixes https://bugs.launchpad.net/juju-core/+bug/1334773
Merge pull request #184 from axw/lp1334773-state-address-networkscope-1.20

state.address.NetworkScope was renamed to

Scope, with no explicit bson field name
specified. This is a schema change, and
broke upgrade from 1.18 to 1.19.

Fixes https://bugs.launchpad.net/juju-core/+bug/1334773
Increment juju stable 1.20 to 1.20.0

Update the stable branch in preparation for the release of 1.20.0
Patch version number in some bootstrap tests to allow tests to pass with non-dev version number
Merge pull request #192 from wallyworld/version-1-20-fix-1.20

Patch version number in some bootstrap tests

Patch the version.Current to a dev version since upload-tools is not allowed for non-dev versions.
More robust HA upgrade in machine agent

If upgrading mongo to HA only partially
completes such that the replicaset is not
initiated, then we would previously failed
on the second attempt. Make sure we use
"Direct" connections when upgrading to HA.

Possibly fixes https://launchpad.net/bugs/1334273
Don't expose the user command yet
Merge pull request #193 from axw/machine-agent-upgrade-ha-robustness-1.20

More robust HA upgrade in machine agent

If upgrading mongo to HA only partially
completes such that the replicaset is not
initiated, then we would previously failed
on the second attempt. Make sure we use
"Direct" connections when upgrading to HA.

Possibly fixes https://launchpad.net/bugs/1334273
Merge pull request #194 from howbazaar/1.20-disable-user

Don't expose the user command yet

Just for the 1.20 release. Still enabled on master.

The user command is undergoing more change with the upcoming identity work. Rather than publicly expose something that we know is changing soon, just keep it disabled.

The enabling was introduced during 1.19.
cmd/jujud: synchronise upgrade steps and ensureMongoServer

It's possible for the upgrade steps to complete before the
state worker starts, thus preventing it from initialising
mongo properly on upgrade. This PR makes it so that the
upgrade steps runner waits for ensureMongoServer to finish
before proceeding.

Maybe fixes https://bugs.launchpad.net/juju-core/+bug/1334273
utils/ssh: set ServerAliveInterval option

Bootstrapping Azure was seeing the CLI
hang at "apt-get upgrade" with no further
output or command completion. Inspection
of cloud-init-output.log on the server
showed that the bootstrap procedure
completed successfully.

The problem appears to be due to the
"apt-get upgrade" taking a long time on
Azure: over 6 minutes. This inactivity
causes the ssh server to discontinue sending
output to the client. To resolve the issue
we need to ensure the ssh client sends
keepalive messages to the server.

Fixes https://bugs.launchpad.net/juju-core/+bug/1316185
provider/azure: use affinity group in vnet site

Revert change based on observations of vnet
related issues. Azure console displays advisory
warning about vnets tied to locations, suggesting
vnets be tied to affinity groups to mitigate.
Merge pull request #202 from axw/lp1334273-upgrade-ha-race-1.20

cmd/jujud: synchronise upgrade steps and ensureMongoServer

It's possible for the upgrade steps to complete before the
state worker starts, thus preventing it from initialising
mongo properly on upgrade. This PR makes it so that the
upgrade steps runner waits for ensureMongoServer to finish
before proceeding.

Maybe fixes https://bugs.launchpad.net/juju-core/+bug/1334273
Merge pull request #204 from axw/azure-network-affinitygroup-1.20

provider/azure: use affinity group in vnet site

Revert change based on observations of vnet
related issues. Azure console displays advisory
warning about vnets tied to locations, suggesting
vnets be tied to affinity groups to mitigate.
Merge pull request #203 from axw/lp1316185-ssh-keepalive-1.20

utils/ssh: set ServerAliveInterval option

Bootstrapping Azure was seeing the CLI
hang at "apt-get upgrade" with no further
output or command completion. Inspection
of cloud-init-output.log on the server
showed that the bootstrap procedure
completed successfully.

The problem appears to be due to the
"apt-get upgrade" taking a long time on
Azure: over 6 minutes. This inactivity
causes the ssh server to discontinue sending
output to the client. To resolve the issue
we need to ensure the ssh client sends
keepalive messages to the server.

Fixes https://bugs.launchpad.net/juju-core/+bug/1316185
Allow restore to retry connecting to state server
Merge pull request #215 from wallyworld/restore-connection-retry-1.20

Allow restore to retry connecting to state server

The restore process recreates a state server but it may not have finished starting everything before attempting to reconnect. So a retry loop is added where needed. Tested live on EC2, first to reproduce the bug and then to verify the fix.

Fixes: https://bugs.launchpad.net/juju-core/+bug/1336104
Increment juju to 1.20.1
Merge pull request #240 from sinzui/inc-1.20.1

Increment juju to 1.20.1

Increment juju stable 1.20 to 1.20.1.