Canonical Juju

Failure to start LXD containers results in incomplete relationships, blocking deployment

Bug #1948955 reported by Moises Emilio Benzan Mora
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Undecided
Unassigned

Bug Description

JuJu fails to start LXD containers which inherently blocks deployments due to missing relationships (in this case). We don't currently know the root cause for this.

First noticed in: https://solutions.qa.canonical.com/testruns/testRun/9df48aff-22c2-47dd-992f-929f02c7c770

Run artifacts: https://oil-jenkins.canonical.com/artifacts/9df48aff-22c2-47dd-992f-929f02c7c770/index.html

See original description
Revision history for this message
Moises Emilio Benzan Mora (moisesbenzan) wrote :

FWIW, Out of dozen containers only one failed to start.

description: updated
tags: added: cdo-qa
Revision history for this message
Konstantinos Kaskavelis (kaskavel) wrote :

Closing this due to inactivity (low number of occurrences, and no hit for more than one year)

tags: added: solutions-qa-expired
Changed in juju:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.