Precise services cannot be deployed

Build: #2187 Revision: gitbranch:master:github.com/juju/juju 24c1b80d Version: 1.22-alpha1 is the first case where all these fail.

The error is in cloud-init-output.log. Both machine 1 and machine 2 of any deployed service has this error:

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
2015-01-05 18:44:08,608 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_landscape

2015-01-05 18:44:08,608 - __init__.py[ERROR]: config handling of landscape, None, [] failed

2015-01-05 18:44:08,609 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_timezone

2015-01-05 18:44:08,609 - __init__.py[ERROR]: config handling of timezone, None, [] failed

2015-01-05 18:44:08,609 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_puppet

2015-01-05 18:44:08,609 - __init__.py[ERROR]: config handling of puppet, None, [] failed

2015-01-05 18:44:08,609 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_chef

2015-01-05 18:44:08,610 - __init__.py[ERROR]: config handling of chef, None, [] failed

2015-01-05 18:44:08,610 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_salt_minion

2015-01-05 18:44:08,610 - __init__.py[ERROR]: config handling of salt-minion, None, [] failed

2015-01-05 18:44:08,611 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_mcollective

2015-01-05 18:44:08,611 - __init__.py[ERROR]: config handling of mcollective, None, [] failed

2015-01-05 18:44:08,611 - __init__.py[WARNING]: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
  File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 70, in handle
ImportError: No module named cc_disable_ec2_metadata

2015-01-05 18:44:08,612 - __init__.py[ERROR]: config handling of disable-ec2-metadata, None, [] failed

2015-01-05 18:44:08,612 - __init__.py[WARNING]: Traceba...

The PR: https://github.com/juju/juju/pull/1205 introduced this bug in commit https://github.com/juju/juju/commit/e6cf44d0
Prompting the install of "cloud-image-utils" in https://github.com/juju/juju/commit/e6cf44d0#diff-64ac36c1eac264218f9546229abd274fR217 , which replaces cloud-utils provokes cloud-init to be uninstalled since it deppends on it.

As per the cloud init output log in comment #2, on a precise system, if you do:

apt-get install cloud-image-utils

apt-decides it needs to remove the cloud-init package (amongst others).

Suggested fix along the lines of:

<smoser> we can fix that with a packaging change to cloud-init in precise.
<smoser> to depend on cloud-image-utils | cloud-utils

For now, I've worked around in Juju by not explicitly installing cloud-image-utils. Where tis matter, in local providers, I've added a check to ensure that cloud-image-utils is installed.

The restricted-network test fails because of the upstream dep. We are changing the test to use trusty (as series is not relevant).