manual provider add-machine fails immediately after bootstrap
Bug #1538583 reported by
Curtis Hovey
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Invalid
|
High
|
Unassigned | ||
1.25 |
Invalid
|
High
|
Unassigned |
Bug Description
As seen in
http://
CI saw errors like this in several manual provider tests. The wily, trusty and precise jobs failed when provisioning in ec2.
2016-01-26 20:31:22 ERROR cmd supercommand.go:448 connection is shut down
2016-01-26 20:31:22 ERROR Command '('juju', '--show-log', 'add-machine', '-m', 'manual-
The trusty ppc4el job passed though.
The offending behaviour is now in master and 1.25. 1.25.4 cannot be released.
Changed in juju-core: | |
status: | New → Incomplete |
summary: |
- manual proovider add-machine failed in api-command-rename + manual provider add-machine failed in api-command-rename |
tags: | added: regression |
Changed in juju-core: | |
status: | Incomplete → Triaged |
no longer affects: | juju-core/api-command-rename |
summary: |
- manual provider add-machine failed in api-command-rename + manual provider add-machine fails immediately after bootstrap |
Changed in juju-core: | |
importance: | Undecided → High |
importance: | High → Critical |
milestone: | none → 2.0-alpha2 |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-beta1 |
Changed in juju-core: | |
milestone: | 2.0-beta1 → 2.0-beta2 |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
milestone: | 2.0-beta2 → 2.0-beta3 |
Changed in juju-core: | |
milestone: | 2.0-beta3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.1 |
Changed in juju-core: | |
assignee: | Dave Cheney (dave-cheney) → nobody |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.1 → none |
milestone: | none → 2.0.1 |
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju-core: | |
status: | Triaged → Invalid |
Changed in juju: | |
milestone: | 2.0.1 → none |
Changed in juju: | |
importance: | High → Medium |
To post a comment you must log in.
I see that the precise jobs all failed because of this error: /juju-qa.jujuci: No such file or directory
The wily job failed due to a "connection is shutdown" error , which makes me wonder if it's related to bug 1517632 (the outdated distro info bug)