co-locate tag in metainfo.xml file for custom service not working as expected.

[Christopher Jackson]

Hi All,

I have created a custom Ambari Service with a master and client component. I 
have the requirement that my master component be installed on the same node 
that has an instance of the OOZIE/OOZIE_SERVER component. I have tried to force 
this by including the following snippet in my services master component 
configuration as part of the meta-info.xml file. However when I go to create a 
new cluster, my master component is placed on a node that doesn’t have 
OOZIE_SERVER component.

<dependency>
        <name>OOZIE/OOZIE_SERVER</name>
        <scope>host</scope>
        <auto-deploy>
                <enabled>true</enabled>
                <co-locate>MY_SERVICE/MY_MASTER_COMPONENT</co-locate>
        </auto-deploy>
</dependency>


Is this not the correct way to enforce such a requirement? Or am I missing some 
additional configuration?

Thanks in advance,

Christopher Jackson