I guess it would be good to also gather some metrics when this script restarts rabbitmq, to have a better view on the memory issue itself.
Diff comments: > diff --git a/mojo/manifest b/mojo/manifest > index c60df1b..b5be817 100644 > --- a/mojo/manifest > +++ b/mojo/manifest > @@ -2,3 +2,8 @@ collect > secrets > bundle config=service-bundle wait=True max-wait=1200 > script config=make-lxd-secgroup > +<<<<<<< mojo/manifest > +======= This looks like remains of a merge conflict :-) > +script config=postdeploy > +script config=rabbitmq-cleanup-setup > +>>>>>>> mojo/manifest -- https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/458627 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:add_rabbitmq_cleanup_to_rabbitmq_unit into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
