Джуджу не удалось удалить связь [закрыто]

Я пытаюсь удалить и заново добавить связь между openstack-приборной панелью и службой идентификации.

У меня есть 2 единицы службы приборной панели, и я сделал из нее кластер высокой доступности, а также у меня есть 2 единицы службы идентификации с подчиненным шармом кластера высокой доступности.

Все 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 я вижу следующее:

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}

Но все же я вижу, что связь все еще существует. Кроме того, при повторном добавлении отношения говорится, что отношение уже существует, поэтому он не может добавить отношение.

Что могло быть не так?

7
задан 18 November 2013 в 04:54

2 ответа

Можете ли вы показать свой статус джуджу после запуска удаления отношения? Скорее всего, есть единица в состоянии ошибки. Если во время удаления произошла ошибка, это не удалит связь. Вам нужно будет запустить juju resolved для этой ошибочной единицы, чтобы продолжить удаление отношения.

0
ответ дан 18 November 2013 в 04:54
  • 1
    Расширение Chrome Уведомлений Libnotify имело демона, который сделал это, но его doesn' t больше работают. Это было в моем вопросе... – Jean 12 May 2015 в 11:09

Я не слишком знаком с Джуджу, но это может помочь или дать вам представление о том, что делать.

https://juju.ubuntu.com/docs/authors-implicit-relations.html

https://juju.ubuntu.com/docs/charms -relations.html

А как насчет "juju destroy-Relations"?

0
ответ дан 18 November 2013 в 04:54

Другие вопросы по тегам:

Похожие вопросы: