unit agent lost after model migration
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
In Progress
|
High
|
Harry Pidcock | ||
| 2.9 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 3.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 3.3 |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
After a successful model migration, it is possible for a unit agent to be lost, despite the machine's agent being present.
Model Controller Cloud/Region Version SLA Timestamp
model-migration
App Version Status Scale Charm Channel Rev Exposed Message
dummy-source blocked 0/1 juju-qa-
Unit Workload Agent Machine Public address Ports Message
dummy-source/0 unknown lost 0 44.223.107.226 agent lost, see 'juju show-status-log dummy-source/0'
Machine State Address Inst id Base AZ Message
0 started 44.223.107.226 i-008dbaf71b9735091 ubuntu@22.04 us-east-1b running
Machine log https:/
Unit log https:/
| Harry Pidcock (hpidcock) wrote | #1 |
https:/