Comment 8 for bug 1347715

Revision history for this message
Curtis Hovey (sinzui) wrote :

The tests still fail as of commit 62e172632c3e9d8496805ed5223f9f4acc28986a
    http://juju-ci.vapour.ws:8080/job/manual-deploy-precise-amd64/944/console
    http://juju-ci.vapour.ws:8080/job/manual-deploy-trusty-ppc64/449/console

The commit is after the commits that tried to fix the manual provider:
    ab7affd5c1fe62729bad99109f1a6b08b528f82e
    dff967dd7713aa99afc04c2387cfe0c73fabba0d
    a03922a72b4e4daa8cadb8cd01c6cfd906fa6ff5

I see this for the ec2 instances that were created up for the test
    2014-07-31 16:44:03 ERROR juju.cmd supercommand.go:323 Warning: Permanently added 'ec2-54-210-191-68.compute-1.amazonaws.com,172.31.37.64' (ECDSA) to the list of known hosts.
    Permission denied (publickey).: subprocess encountered error code 255

I see this for the ppc machines that were selects for the test
    2014-07-31 17:21:40 INFO juju.environs.manual init.go:121 series: trusty, characteristics: arch=ppc64 cpu-cores=1 mem=8166M
    2014-07-31 17:21:41 ERROR juju.cmd supercommand.go:323 Permission denied (publickey).: subprocess encountered error code 255