unit stuck with status installing agent after series upgrade

Bug #1750907 reported by Heather Lanigan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Heather Lanigan

Bug Description

After following the series upgrade instructions for an existing workload, the unit gets stuck here:

Unit Workload Agent Machine Public address Ports Message
ubuntu/0* waiting idle 0 10.63.22.17 installing agent

Found during work on lp: 1749201

Tags: uosci
Changed in juju:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Heather Lanigan (hmlanigan)
milestone: none → 2.3.4
Changed in juju:
status: Triaged → In Progress
Ryan Beisner (1chb1n)
tags: added: uosci
Changed in juju:
milestone: 2.3.4 → 2.3.5
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

A programatic fix for this has been ruled out as it's also possible to resolve with additional scripting for the series upgrade.

When moving from trusty to xenial, the same steps for the machine service should be followed for the unit service as well. Where the machine service is named: jujud-machine-<machine #>, the unit service is called: jujus-unit-<application name>-<unit #>.

Online docs are being updated accordingly:
https://github.com/juju/docs/pull/2470

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
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.