juju-core

juju upgrage-juju --upload-tools hangs with jes flag

  1. Series trunk
  2. Bug #1453634
Bug #1453634 reported by Jesse Meek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Status tracked in Trunk
Trunk
Invalid
High
Jesse Meek

Bug Description

On EC2 provider:

$ juju --show-log upgrade-juju --upload-tools
2015-05-11 01:04:43 INFO juju.cmd supercommand.go:37 running juju [1.25-alpha1-trusty-amd64 gc]
2015-05-11 01:04:43 INFO juju.api api.go:280 connecting to API addresses: [107.20.64.80:17070 10.230.165.190:17070]
2015-05-11 01:04:43 INFO juju.api apiclient.go:331 dialing "wss://107.20.64.80:17070/environment/8ae205a1-2887-4b4e-82ad-dffffca7ee6e/api"
2015-05-11 01:04:43 INFO juju.api apiclient.go:331 dialing "wss://10.230.165.190:17070/environment/8ae205a1-2887-4b4e-82ad-dffffca7ee6e/api"
2015-05-11 01:04:44 INFO juju.api apiclient.go:263 connection established to "wss://107.20.64.80:17070/environment/8ae205a1-2887-4b4e-82ad-dffffca7ee6e/api"
2015-05-11 01:04:49 INFO juju.environs.tools build.go:167 found existing jujud
2015-05-11 01:04:49 INFO juju.environs.tools build.go:177 target: /tmp/juju-tools094751944/jujud
2015-05-11 01:04:56 INFO juju.environs.sync sync.go:323 built tools 1.25-alpha1.3-trusty-amd64 (15785kB)
2015-05-11 01:04:56 INFO juju.cmd.juju upgradejuju.go:326 uploading tools 1.25-alpha1.3-trusty-amd64 (15785kB) to Juju state server
available tools:
    1.25-alpha1.3-trusty-amd64
best version:
    1.25-alpha1.3
2015-05-11 01:23:43 INFO juju.rpc server.go:328 error closing codec: write tcp 107.20.64.80:17070: broken pipe
2015-05-11 01:23:43 ERROR juju.cmd supercommand.go:430 error receiving message: read tcp 107.20.64.80:17070: connection timed out

The new tools are upload, but the old tools are not upgraded. So you can then:

$ juju upgrade-juju --version="1.25-alpha1.3"

Which upgrades the tools.

Jesse Meek (waigani)
Changed in juju-core:
milestone: 1.25.0 → 1.24.0
milestone: 1.24.0 → 1.25.0
Revision history for this message
Andrew Wilkins (axwalk) wrote :

I don't understand what the problem is. It appears you had a network connection error during upgrade, which caused the command to fail. Is there more to it?

I've just run "juju upgrade-juju --upload--tools" on the tip of the 1.24 branch, and it works fine.

Revision history for this message
Jesse Meek (waigani) wrote :

I've tried about 4 times in a row - same issue each time. I can ssh to machine 0, debug-log works, but it always hangs on upgrade-juju --upload-tools.

Revision history for this message
Jesse Meek (waigani) wrote :

This seems to only be happening on my box, so knocking down the importance.

Revision history for this message
Jesse Meek (waigani) wrote :

I had the following in my .bashrc:

export JUJU_DEV_FEATURE_FLAGS=jes

Commenting this out and re-sourcing removed the bug. Thus, I think something hiding behind the jes flag is breaking upgrade-juju

summary: - juju upgrage-juju --upload-tools hangs
+ juju upgrage-juju --upload-tools hangs with jes flag
no longer affects: juju-core/1.24
Revision history for this message
Cheryl Jennings (cherylj) wrote :

I was able to reproduce this myself yesterday with EC2, but haven't been able to today after 4 tries.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.