Juju allows upgrade based on stream, but fails to find agent binaries

Bug #1890452 reported by Joseph Phillips
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Undecided
Unassigned

Bug Description

Using version 2.8.1, with 2.8.2 currently proposed and in QA.

$ juju upgrade-controller
no upgrades available

$ juju upgrade-controller --agent-stream=proposed --debug
...
16:34:28 DEBUG juju.cmd.juju.commands upgrademodel.go:737 searching for "proposed" agent binaries with major: 2
16:34:34 DEBUG juju.cmd.juju.commands upgrademodel.go:864 found more recent current version 2.8.2
...

At this point the upgrade is allowed to proceed, but based on the logs we do not attempt to locate agent binaries in the correct stream:

machine-0: 16:34:43 DEBUG juju.environs.tools finding agent binaries in stream: "released"
machine-0: 16:34:43 DEBUG juju.environs.tools reading agent binaries with major version -1
machine-0: 16:34:43 DEBUG juju.environs.tools filtering agent binaries by version: 2.8.2
machine-0: 16:34:43 DEBUG juju.environs.tools filtering agent binaries by series: bionic
machine-0: 16:34:43 DEBUG juju.environs.tools filtering agent binaries by architecture: amd64
machine-0: 16:34:43 DEBUG juju.environs.tools trying datasource "keystone catalog"
machine-0: 16:34:44 DEBUG juju.environs.simplestreams using default candidate for content id "com.ubuntu.juju:released:tools" are {20161007 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
...
machine-0: 16:34:44 DEBUG juju.worker.dependency "upgrader" manifold worker stopped: no matching agent binaries available
machine-0: 16:34:44 ERROR juju.worker.dependency "upgrader" manifold worker returned unexpected error: no matching agent binaries available

Tags: upgrade-juju
Revision history for this message
Joseph Phillips (manadart) wrote :

So what happens here is the upgrader worker watches the model config for changes. If the version changes, it simply requests tools for the version.

Nowhere is it stored that we requested the upgrade from the specific stream, instead at this point, we just use the configured model value (default=released) for "agent-stream".

Changing this value to mirror that supplied at the CLI allows the upgrade to proceed.

Changed in juju:
status: New → Triaged
Ian Booth (wallyworld)
tags: added: upgrade-juju
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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