upgrade to 1.17.0 fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth |
Bug Description
The CI upgrade-juju from 1.16.3 to 1.17.0 failed on canonistack. The last successful test was against r2052. r2053 (https:/
We can see in the log that 1.17.0.
We can see in the log that the tools-metadata-url is used and the path is correct /juju-dist/
We also know that the config has an identical tools-url set
We can see in the logs that tools-url is empty (as is public-bucket-url)
We can see the bootstrap node searching for tools and it never uses /juju-dist/
We see juju looking in /juju-dist/tools from many locations.
Maybe the upgraded client sees the tools using the new config, and updates the jenv. The jenv is passed to the server agent. It cannot upgrade because it does not know about tools-metadata-url yet.
EXAMPLE LAST SUCCESS r2052
http://
EXAMPLE FAILURE r2053
http://
Related branches
- Juju Engineering: Pending requested
-
Diff: 78 lines (+18/-14)2 files modifiedenvirons/config/config.go (+3/-1)
environs/config/config_test.go (+15/-13)
description: | updated |
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
The local config != the config that is in Mongodb. You can check that with "juju get-environment". url/tools- url locally, but *not* setting it inside mongo (juju set-environment tools-url=XXX").
My guess is that you are setting a tools-metadata-
I would have thought this wouldn't have been working for a lot longer. But perhaps you were bootstrapping with tools-url set before?