Joyent deploys fail in CI
Bug #1402495 reported by
Menno Finlay-Smits
This bug report is a duplicate of:
Bug #1396099: AWS/Joyent/HP/manual/maas: juju deploy error "connection is shut down".
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
New
|
Critical
|
Unassigned | ||
Bug Description
The joyent-deploy-* CI jobs fail on master because the command to deploy the dummy-source charm fails with a non-zero exit code.
An example:
http://
I haven't been able to reproduce this when deploying to Joyent from my own machine (approximately copying what the test does). It might be worth trying to reproduce this by running the actual test (deploy_job.py) from using the real CI infrastructure.
The same test works fine for 1.21 so there is some kind of regression for master.
| description: | updated |
To post a comment you must log in.
