ccp deploy hangs when multiple containers defined in service.yaml with cross-dependencies

If we define multiple containers in single service yaml, with cross-dependencies (service B -> service A), ccp deploy will hang forever.

service:
  name: rabbitmq
  kind: DaemonSet
  ports:
    - {{ rabbitmq.port }}
  containers:
    - name: rabbitmq
      image: rabbitmq
      probes:
        readiness: "/opt/ccp/bin/rabbitmq-readiness.sh"
        liveness:
          command: "/opt/ccp/bin/rabbitmq-liveness.sh"
          type: "exec"
      volumes:
        - name: rabbitmq-logs
          path: "/var/log/ccp/rabbitmq"
          type: host
          readOnly: False
      pre:
        - name: chown-logs-dir
          command: "sudo /bin/chown rabbitmq: /var/log/ccp/rabbitmq"
      daemon:
        dependencies:
          - etcd
        command: /usr/lib/rabbitmq/bin/rabbitmq-server
        files:
          - rabbitmq-conf
          - erlang-cookie
          - rabbitmq-env-conf
          - enabled-plugins
          - rabbitmq-readiness
          - rabbitmq-liveness
          - rabbitmq-check-helpers
      post:
        - name: create-startup-marker
          command: "date +%s > /tmp/rabbit-startup-marker"
    - name: rabbitmq-exporter
      image: rabbitmq
      daemon:
        dependencies:
          - rabbitmq
        command: /var/lib/rabbitmq/golang/bin/rabbitmq_exporter

$ ccp --config ccp.conf --verbose --debug deploy -c rabbitmq
[...]
2016-11-14 11:41:34,259 INFO fuel_ccp.validation.service Validation of service definitions for 1 components passed successfully!