我正在尝试删除并重新添加 openstack-dashboard 和身份服务之间的关系。
我有 2 个仪表板服务单元，并已用它组建了一个 HA 集群，另外我还有 2 个身份服务单元以及 HA 集群下属魅力。
所有 4 个单元都处于“已启动”状态，而不是错误状态。
我尝试运行以下命令：
xsmaas01:~$ sudo juju remove-relation openstack-dashboard keystone --debug
[sudo] password for sonali:
2013-11-05 12:31:11 DEBUG juju.provider.maas environprovider.go:32 opening environment "maas".
2013-11-05 12:31:11 DEBUG juju state.go:160 waiting for DNS name(s) of state server instances [/MAAS/api/1.0/nodes/node-bc3afec8-19f2-11e3-8cf9-c6d6cdbfe570/]
2013-11-05 12:31:11 INFO juju.state open.go:68 opening state; mongo addresses: ["jujuzk.master:37017"]; entity ""
2013-11-05 12:31:11 INFO juju.state open.go:106 connection established
2013-11-05 12:31:11 INFO juju supercommand.go:286 command finished
在 juju debug-log 中我看到了这个：
jujuzk:2013-11-05 12:30:41 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"RequestId":37,"Type":"Pinger","Request":"Ping","Params":{}}
jujuzk:2013-11-05 12:30:41 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":37,"Response":{}}
jujuzk:2013-11-05 12:30:41 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"RequestId":37,"Type":"Pinger","Request":"Ping","Params":{}}
jujuzk:2013-11-05 12:30:41 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":37,"Response":{}}
opdashboard01:2013-11-05 12:31:23 DEBUG juju filter.go:311 worker/uniter/filter: got relations change
opdashboard01:2013-11-05 12:31:23 DEBUG juju filter.go:339 worker/uniter/filter: sent relations event
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-broken" hook
opdashboard01:2013-11-05 12:31:23 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-broken" hook (not implemented)
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-broken" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:365 worker/uniter: committing "relation-broken" hook
opdashboard01:2013-11-05 12:31:23 INFO juju uniter.go:383 worker/uniter: committed "relation-broken" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opks03:2013-11-05 12:31:33 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opks03:2013-11-05 12:31:33 DEBUG juju filter.go:311 worker/uniter/filter: got relations change
opks03:2013-11-05 12:31:33 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opks03:2013-11-05 12:31:33 DEBUG juju filter.go:339 worker/uniter/filter: sent relations event
opks03:2013-11-05 12:31:33 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opks03:2013-11-05 12:31:33 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-broken" hook
opks03:2013-11-05 12:31:33 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-broken" hook (not implemented)
opks03:2013-11-05 12:31:33 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-broken" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:365 worker/uniter: committing "relation-broken" hook
opks03:2013-11-05 12:31:33 INFO juju uniter.go:383 worker/uniter: committed "relation-broken" hook
opdashboard02:2013-11-05 12:31:26 DEBUG juju filter.go:311 worker/uniter/filter: got relations change
opdashboard02:2013-11-05 12:31:26 DEBUG juju filter.go:339 worker/uniter/filter: sent relations event
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:383 worker/uniter: committed "relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-broken" hook
opdashboard02:2013-11-05 12:31:26 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-broken" hook (not implemented)
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-broken" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:365 worker/uniter: committing "relation-broken" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:383 worker/uniter: committed "relation-broken" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:350 worker/uniter: running "identity-service-relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju context.go:174 worker/uniter: skipped "identity-service-relation-departed" hook (not implemented)
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:358 worker/uniter: ran "identity-service-relation-departed" hook
opdashboard02:2013-11-05 12:31:26 INFO juju uniter.go:365 worker/uniter: committing "relation-departed" hook
opks01:2013-11-05 12:32:19 DEBUG juju filter.go:311 worker/uniter/filter: got relations change
jujuzk:2013-11-05 12:31:32 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"RequestId":38,"Type":"Pinger","Request":"Ping","Params":{}}
jujuzk:2013-11-05 12:31:32 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":38,"Response":{}}
jujuzk:2013-11-05 12:31:38 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"RequestId":13,"Type":"Pinger","Request":"Ping","Params":{}}
jujuzk:2013-11-05 12:31:38 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":13,"Response":{}}
jujuzk:2013-11-05 12:32:31 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"Type":"Client","Request":"SetAnnotations","Params":{"Tag":"service-openstack-dashboard","Pairs":{"gui-x":"1917.0029802730883","gui-y":"-470.82699030543813"}},"RequestId":41}
jujuzk:2013-11-05 12:32:31 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":41,"Response":{}}
jujuzk:2013-11-05 12:32:32 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"RequestId":39,"Type":"Pinger","Request":"Ping","Params":{}}
jujuzk:2013-11-05 12:32:32 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":39,"Response":{}}
jujuzk:2013-11-05 12:32:35 DEBUG juju codec.go:168 rpc/jsoncodec: -> {"RequestId":5,"Response":{"Deltas":[["annotation","change",{"Tag":"service-openstack-dashboard","Annotations":{"gui-x":"1917.0029802730883","gui-y":"-470.82699030543813"}}]]}}
jujuzk:2013-11-05 12:32:35 DEBUG juju codec.go:103 rpc/jsoncodec: <- {"Type":"AllWatcher","Request":"Next","Id":"1","Params":{},"RequestId":42}
但我仍然可以看到关系仍然存在。此外，如果重新添加关系，它会说关系已经存在，因此无法添加关系。
可能出了什么问题？
答案1
运行删除关系后，您可以显示您的 juju 状态吗？很可能有一个单元处于错误状态。如果单元在删除过程中出错，则不会删除关系。您需要juju resolved针对该错误单元运行，才能继续删除关系。
答案2
我不太熟悉 Juju，但这可能会有所帮助或让你知道该做什么。
https://juju.ubuntu.com/docs/authors-implicit-relations.html
https://juju.ubuntu.com/docs/charms-relations.html
那么“juju destroy-relation” 怎么样？