ampq_config.py is created 0600 by root and can't be read by the upstart job running as nobody/nogroup

Fix in progress but a new bug surfaces:

Traceback (most recent call last):
  File "./branch-source-builder/bsbuilder/run_worker.py", line 91, in <module>
    amqp_utils.process_queue(config, 'bsbuilder', on_message)
  File "/srv/bsb_worker/ci-utils/ci_utils/amqp_utils.py", line 101, in process_queue
    conn = connection(config)
  File "/srv/bsb_worker/ci-utils/ci_utils/amqp_utils.py", line 48, in connection
    password=rabbit_config.AMQP_PASSWORD
  File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py", line 144, in __init__
    (10, 30), # tune
  File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/abstract_channel.py", line 95, in wait
    self.channel_id, allowed_methods)
  File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py", line 202, in _wait_method
    self.method_reader.read_method()
  File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py", line 221, in read_method
    raise m
IOError: Socket closed

With the fix in progress the amqp_config.py is created with 0644 and its content seems fine to me:

# DO NOT EDIT. Generated by restish charm hook
AMQP_USER = "xxx"
AMQP_VHOST = "/"
AMQP_HOST = "10.0.0.243"
AMQP_PASSWORD = "xxx"

or is it an issue with the IP address ?

But again, why would this causes an issue *now* and not earlier ?

Slipt the new bug into bug #1290386