| 2016-02-05 22:18:01 |
Curtis Hovey |
bug |
|
|
added bug |
| 2016-02-09 14:18:23 |
Curtis Hovey |
summary |
aws-deploy-trusty-amd64-on-xenial-amd64 hooks not firing |
juju ssh to wily/xenial broken |
|
| 2016-02-09 14:20:10 |
Curtis Hovey |
description |
As seen in
http://reports.vapour.ws/releases/issue/563c4dc1749a5669a5aed8a7
CI's dummy charms exchange a random token when hooks fire. This allows the test know hooks fire and that charms can respond to them. Ci occasionally sees the exchange fail, but a recent change in master is making a single test fail, aws-deploy-trusty-amd64-on-xenial-amd64. For example:
http://reports.vapour.ws/releases/3579/job/aws-deploy-trusty-amd64-on-xenial-amd64/attempt/186
The token check passes for all other jobs, including more than 10 in aws and 4 deploying xenial or wily. I changed the job to try xenial and wily series, but the job fails. |
As seen in
http://reports.vapour.ws/releases/issue/563c4dc1749a5669a5aed8a7
CI's dummy charms exchange a random token when hooks fire. This allows the test know hooks fire and that charms can respond to them. Ci occasionally sees the exchange fail, but a recent change in master is making a single test fail, aws-deploy-trusty-amd64-on-xenial-amd64. For example:
http://reports.vapour.ws/releases/3579/job/aws-deploy-trusty-amd64-on-xenial-amd64/attempt/186
Using an updated test script, we can see that "juju ssh" to the unit is failing. When the script falls back to ssh, it can read the token. |
|
| 2016-02-09 14:20:55 |
Curtis Hovey |
description |
As seen in
http://reports.vapour.ws/releases/issue/563c4dc1749a5669a5aed8a7
CI's dummy charms exchange a random token when hooks fire. This allows the test know hooks fire and that charms can respond to them. Ci occasionally sees the exchange fail, but a recent change in master is making a single test fail, aws-deploy-trusty-amd64-on-xenial-amd64. For example:
http://reports.vapour.ws/releases/3579/job/aws-deploy-trusty-amd64-on-xenial-amd64/attempt/186
Using an updated test script, we can see that "juju ssh" to the unit is failing. When the script falls back to ssh, it can read the token. |
As seen in
http://reports.vapour.ws/releases/issue/563c4dc1749a5669a5aed8a7
CI's dummy charms exchange a random token when hooks fire. This allows the test know hooks fire and that charms can respond to them. Ci occasionally sees the exchange fail, but a recent change in master is making a single test fail, aws-deploy-trusty-amd64-on-xenial-amd64. For example:
http://reports.vapour.ws/releases/3579/job/aws-deploy-trusty-amd64-on-xenial-amd64/attempt/186
Using an updated test script, we can see that "juju ssh" to the unit is failing. When the script falls back to ssh, it can read the token.
Changing the services to trusty works. changing the services to wily or xenial fails. |
|
| 2016-02-09 14:30:47 |
Curtis Hovey |
nominated for series |
|
juju-core/1.25 |
|
| 2016-02-09 14:30:47 |
Curtis Hovey |
bug task added |
|
juju-core/1.25 |
|
| 2016-02-09 14:34:44 |
Curtis Hovey |
tags |
ci ec2-provider hooks regression wily xenial |
ci ec2-provider regression ssh wily xenial |
|
| 2016-02-11 02:38:14 |
Curtis Hovey |
juju-core: status |
Triaged |
Invalid |
|
| 2016-02-11 02:38:18 |
Curtis Hovey |
juju-core: milestone |
2.0-alpha2 |
|
|
| 2016-05-03 13:37:01 |
Curtis Hovey |
juju-core/1.25: status |
New |
Fix Released |
|
