juju-updateseries ERROR JUJU_CONTEXT_ID not set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
juju-updateseries is failing with JUJU_CONTEXT_ID not set
$ juju add-model test
Added 'test' model on snowspeeder/
$ juju model-config default-
$ juju deploy cs:ubuntu
Located charm "cs:ubuntu-12".
Deploying charm "cs:ubuntu-12".
$ juju status ubuntu
Model Controller Cloud/Region Version SLA Timestamp
test snowspeeder-
App Version Status Scale Charm Store Rev OS Notes
ubuntu 16.04 active 1 ubuntu jujucharms 12 ubuntu
Unit Workload Agent Machine Public address Ports Message
ubuntu/0* active idle 0 192.168.10.11 ready
Machine State DNS Inst id Series AZ Message
0 started 192.168.10.11 juju-f98ed8-0 xenial Running
$ juju ssh ubuntu/0 sudo do-release-upgrade -f DistUpgradeView
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1246 kB]
Fetched 1247 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
MarkInstall libpam-cap [ amd64 ] < none -> 1:2.25-1.2 > ( libs ) FU=1
...
Processing triggers for systemd (237-3ubuntu10.11) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Connection to 192.168.10.11 closed.
$ juju ssh ubuntu/0 -- sudo juju-updateseries --from-series xenial --to-series bionic --start-agents
sudo: unable to resolve host juju-f98ed8-0
ERROR JUJU_CONTEXT_ID not set
Connection to 192.168.10.11 closed.
This environment is using juju 2.6-beta1, but this behavior is being seen in 2.4 and 2.5
Changed in juju: | |
status: | Incomplete → Triaged |
importance: | Undecided → Low |
Are you updating the series from a client or from the machine itself? The client is required to help manage the flow as the agent will go down and restart. I'm not sure it's viable to do it from the machine you're actually upgrading?