Services not running that should be: tvault-contego
Bug #1951999 reported by
Corey Bryant
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TrilioVault Data Mover Charm |
Confirmed
|
High
|
Abhijeet Patra | ||
Bug Description
trilio-data-mover/2 blocked idle 172.16.255.217 Services not running that should be: tvault-contego
Seen at:
https:/
https:/
https:/
https:/
A restart of tvault-contego appears to be successful and lasting.
| tags: | added: unstable-test |
| description: | updated |
| Changed in charm-trilio-data-mover: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Liam Young (gnuoy) wrote | #1 |
Revision history for this message
| Marian Gasparovic (marosg) wrote | #2 |
| tags: | added: cdo-qa foundations-engine |
| Changed in charm-trilio-data-mover: | |
| assignee: | nobody → Abhijeet Patra (abhijeet-trilio) |
| status: | Triaged → Confirmed |
To post a comment you must log in.
What appears to be happening is that the nova-compute charm finished configuring nova.conf after systemd has given up restarting tvault-contego. Unfortunately there is no existing mechanism for the nova-compute charm to request a restart of the subordinate as it is related via the juju-info relation.