Deployer tried to deploy to an non-existant service
Bug #1534623 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
| juju-deployer |
Invalid
|
Low
|
Unassigned | ||
Bug Description
As seen at
http://
Juju CI is seeing messages like this:
deployer.
Juju probably failed to deploy the first service to the instance, but continued trying to deploy other services to the instance. As this issue seen in several Juju's this might be an issue in deployer. The host machine was probably under load at the time of the openstack deployment.
| tags: | added: 2.0-count |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
| affects: | juju-core → juju |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #1 |
| Changed in juju-deployer: | |
| status: | New → Invalid |
| importance: | Undecided → Low |
To post a comment you must log in.
Marking as invalid in juju-deployer, as I believe this would now use native juju bundles