TestDyingMachine fails when unit agent is running on machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
Tests on go-bot are failing in cmd/jujud/
Somehow the deployer in the test getting at the unit-agent running on the machine and trying to interact with it:
[LOG] 19.19979 INFO juju.worker.
[LOG] 19.20017 DEBUG juju rpc/jsoncodec: <- {"RequestId"
[LOG] 19.20024 DEBUG juju rpc/jsoncodec: <- {"RequestId"
[LOG] 19.20256 DEBUG juju rpc/jsoncodec: -> {"RequestId"
[LOG] 19.20282 INFO juju.worker.
[LOG] 19.20390 ERROR juju worker: fatal "deployer": remove /etc/init/
For the full log, see:
<https:/
Related branches
- Juju Engineering: Pending requested
-
Diff: 74 lines (+21/-2)3 files modifiedcmd/jujud/machine_test.go (+0/-1)
cmd/jujud/main_test.go (+16/-0)
worker/deployer/simple.go (+5/-1)
Changed in juju-core: | |
status: | Confirmed → Triaged |
tags: | added: test-failure |
Changed in juju-core: | |
milestone: | 1.17.1 → 1.18.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
milestone: | 1.18.0 → 1.17.3 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
I have skipped out the test on trunk for now, so the bot can land things.