There needs to be a way to remove a suborinate charm short of destroying the primary service.
Trying to remove the relationship:
juju remove-relation nrpe-external-master:nrpe-external-master apache2:nrpe-external-master
2013-01-16 23:58:35,664 WARNING OpenStack identity service not using secure transport
2013-01-16 23:58:35,664 INFO Connecting to environment...
2013-01-16 23:58:35,954 WARNING OpenStack compute service not using secure transport
2013-01-16 23:58:35,954 WARNING OpenStack object-store service not using secure transport
2013-01-16 23:58:36,639 INFO Connected to environment.
2013-01-16 23:58:36,780 ERROR Unsupported attempt to destroy subordinate service 'apache2' while principal service 'nrpe-external-master' is related.
Trying to remove the subordinate service:
(productsearch)prodstack-u1@wekufe:~$ juju destroy-service nrpe-external-master
2013-01-16 23:59:19,812 WARNING OpenStack identity service not using secure transport
2013-01-16 23:59:19,813 INFO Connecting to environment...
2013-01-16 23:59:20,048 WARNING OpenStack compute service not using secure transport
2013-01-16 23:59:20,048 WARNING OpenStack object-store service not using secure transport
2013-01-16 23:59:20,716 INFO Connected to environment.
2013-01-16 23:59:20,796 ERROR Unsupported attempt to destroy subordinate service 'nrpe-external-master' while principal service 'apache2' is related.
Only destroying the primary charm service will work.
There needs to be a way to do this without destroying the primary service. This is a rational expectation I think many besides myself will have.
Its unlikely this will be supported anytime soon, at least at minimum
without new hooks for things like uninstall, which isn't currently planned.
On Thu, Jan 17, 2013 at 7:47 AM, Haw Loeung <email address hidden>wrote:
> ** Tags added: canonical-
>
> --
> You received this bug notification because you are subscribed to juju.
> https:/
>
> Title:
> Support method of removing a subordinate charm
>
> To manage notifications about this bug go to:
> https:/
>