#13023 Raise/disable wiki rate limits on coconut user
Closed: Upstream by adamwill. Opened by adamwill.

Describe what you would like us to do:


Raise or disable the wiki rate limits on the 'coconut' user. I can see how to do this in theory, but it seems we have to apply the config to a user group. coconut isn't in any special user groups, and user group memberships don't seem to be specified in ansible - I assume they're done manually. So I can't fix this myself or send a PR to do it. I guess we can either add coconut to the bot group (which currently contains only 'wikibot') and raise or disable rate limits on that group, or create a new group for this purpose.

The rate limit becomes a problem whenever there's a problem with the wiki and I have to disable the result reporter for a while. When I turn it back on it does a lot of edits when 'catching up' with messages that piled up while it was turned off. This is more common on staging than prod, but it has happened in prod before.

When do you need this to be done by? (YYYY/MM/DD)


No specific date.


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

From what I can see the rate limit is 90 per. minute ... I assume there's no way to limit the reporter in code, to 50 a minute or something? Or detect it hits the ratelimit and waits a minute (hopefully also not processing more messages)?

Adding it to the bot group and making that unlimited seems like a fine workaround to me.

Hmm, for some reason I thought the default limits were per hour, not minute. Per hour would be a bit awkward to handle that way, but per minute is probably doable. I'll see if I can manage something along those lines, then.

https://pagure.io/fedora-qa/fedora_openqa/pull-request/116 should fix this.

Merged that PR, so hopefully this should be addressed now.

Metadata Update from @adamwill:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

Metadata