Merge ~andersson123/autopkgtest-cloud:cache-amqp-fix into autopkgtest-cloud:master
Proposed by
Tim Andersson
Status: | Merged |
---|---|
Merged at revision: | ea3422504760925873da0b96b8a6ef59576f64c4 |
Proposed branch: | ~andersson123/autopkgtest-cloud:cache-amqp-fix |
Merge into: | autopkgtest-cloud:master |
Diff against target: |
108 lines (+46/-2) 4 files modified
charms/focal/autopkgtest-web/config.yaml (+6/-0) charms/focal/autopkgtest-web/reactive/autopkgtest_web.py (+3/-0) charms/focal/autopkgtest-web/webcontrol/cache-amqp (+36/-2) mojo/service-bundle (+1/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Brian Murray | Approve | ||
Paride Legovini | Disapprove | ||
Review via email:
|
To post a comment you must log in.
AFAICT currently the autopkgtest-cloud service would keep working fine if the web workers are down, as those are only used for user interaction. Here we add an dependency on the web units being up, in order for the process to work, and I think we don't want this.
Also: loading the queue contents in two very different ways depending on whether the unit is leader or not will make debugging difficult.
The AutopkgtestQueu eContents class already has checks for leader, adding an "external" check like proposed here calls for other changes in that logic.
What I think is that there should be another way to query rabbitmq for queue length, without popping / pushing all the queue items.