Juju cannot deploy to any substrate

[Curtis Hovey]

A commit ericsnowcurrently/fix-1450092-cloudinit.. was reverted in 1.24. It was also merged into 1.23 and master. The cloud init change prevent juju from deploying to any substrate. Only the manual provider works.

In 1.23: Commit ba9267f Merge pull request #2235 from ericsnowcurrently/fix-1450092-cloudinit…
In master: Commit ebfc363 Merge pull request #2358 from ericsnowcurrently/fix-1450092-cloudinit… …

[Dimiter Naydenov (dimitern)]

Bug 1457011 is most definitely related to this, but not the only cause most likely.

[Eric Snow (ericsnowcurrently)]

http://reviews.vapour.ws/r/1727/ is where the change was reverted on 1.24.

[Curtis Hovey (sinzui)]

We can see commit 3bc3244 is being tested now and deploy is still broken in 1.23.
    http://reports.vapour.ws/releases/2674

[Dimiter Naydenov (dimitern)]

Why is https://github.com/juju/juju/pull/2397 reintroducing the bashisms in init system discovery? We'll start getting '[[: not found' again!

[Eric Snow (ericsnowcurrently)]

The revert simply gets the repo back to a known good state. Addressing the bash-isms will be handled separately.

[Canonical Juju QA Bot (juju-qa-bot)]

Juju-CI verified that this issue is Fix Released in juju-core 1.23:
    http://reports.vapour.ws/releases/2677

[Canonical Juju QA Bot (juju-qa-bot)]

Juju-CI verified that this issue is Fix Released in juju-core master:
    http://reports.vapour.ws/releases/2679