+1 if there's any way we can provide a script to automate this then I'd suggest to go that route. The less we ask users to do the better and I know some folks internally are running 1.23 and a tested/scripted upgrade tool would be useful to share around.
Rick On Fri, 26 Jun 2015, Charles Butler wrote: > Menno, > > This is a good find to raise publicly; however I wonder if we couldn't > offer something up to users that are being caught by this rather than a > suggested workaround, and more as a "Run this patch to correct the issue" - > as these things look like they can be scripted, and included in the 1.23 > release as a patch. > > I however don't know the level of effort involved in that. > > All the best, > > > Charles Butler <[email protected]> - Juju Charmer > Come see the future of datacenter orchestration: http://jujucharms.com > > On Fri, Jun 26, 2015 at 12:45 AM, Menno Smits <[email protected]> > wrote: > > > All, > > > > Due to a new worker that was added in 1.23, it is likely that the state > > server agents will be unable to restart when an upgrade of a 1.23 > > environment is requested. > > > > Manual intervention will be required to unstick the upgrade. On each state > > server host do the following: > > > > - Find the tools directory. > > - For the local provider this will be something like > > ~/.juju/local/tools > > - For other providers this will be /var/lib/juju/tools > > - You should see both the old and the new tools listed with a > > symlink for the machine agent pointing to the old version. For example: > > > > drwxr-xr-x 2 root root 4096 May 27 21:18 1.23.3.1-trusty-amd64 > > drwxr-xr-x 2 root root 4096 Jun 16 11:35 1.24.0-trusty-amd64 > > lrwxrwxrwx 1 root root 21 May 27 21:18 machine-0 -> > > 1.23.3.1-trusty-amd64 > > > > - Remove the old symlink, e.g.: sudo rm machine-0 > > - Add one that points to the new tools, e.g.: sudo ln -s > > 1.24.0-trusty-amd64 machine-0 > > - Kill the machine agent so that it restarts into the new version: > > sudo pkill jujud > > > > The upgrade will then proceed as normal. > > > > It's regrettable that this is required. Unfortunately but because upgrades > > themselves get blocked we can't easily offer an upgrade that fixes the > > problem. > > > > The root cause was fixed in 1.24.0 so upgrading directly to 1.24.0 or > > later (skipping 1.23) will avoid the issue. > > > > - Menno > > > > > > -- > > Juju mailing list > > [email protected] > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/juju > > > > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
