juju-updateseries ERROR JUJU_CONTEXT_ID not set

Bug #1814178 reported by Felipe Reyes
6
This bug affects 1 person
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/snowspeeder with credential 'snowspeeder' for user 'admin'
$ juju model-config default-series=xenial
$ 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-snowspeeder snowspeeder/snowspeeder 2.6-beta1 unsupported 17:48:23-03:00

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 DistUpgradeViewNonInteractive 2>&1 | tee do-release-upgrade.log
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

Revision history for this message
Richard Harding (rharding) wrote :

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?

Revision history for this message
Richard Harding (rharding) wrote :

Actually, you've bypassed the upgrade series feature entirely from what I can see here.

Please see https://docs.jujucharms.com/2.5/en/upgrade-series and let me know if I'm misunderstanding your issue. Marking incomplete pending feedback.

Changed in juju:
status: New → Incomplete
Revision history for this message
Felipe Reyes (freyes) wrote : Re: [Bug 1814178] Re: juju-updateseries ERROR JUJU_CONTEXT_ID not set

On Thu, 2019-01-31 at 22:35 +0000, Richard Harding wrote:
> Actually, you've bypassed the upgrade series feature entirely from
> what
> I can see here.
>
> Please see https://docs.jujucharms.com/2.5/en/upgrade-series and let
> me
> know if I'm misunderstanding your issue. Marking incomplete pending
> feedback.

This is quite different from the document we were using
https://docs.jujucharms.com/2.4/en/howto-updateseries , the user that
found this issue was following that howto.

I will try with the one you pointed out.

Revision history for this message
Felipe Reyes (freyes) wrote :

Once I used "juju update-series" before trying to use "juju ssh app/N -- sudo juju-updateseries ..." things worked.

So my question now is if it's possible to make the error message more informative, at least for 2.5 or 2.6

Changed in juju:
status: Incomplete → Triaged
importance: Undecided → Low
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

tags: added: expirebugs-bot
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.