#11739 fas2discourse group sync adding and removing people very frequently
Closed: Fixed a year ago by dkirwan. Opened a year ago by mattdm.

I don't have direct access to the logs

This is apparently causing a number of issues, including people's "title" changing, spurious trust-level notifications, and possibly problems with moderation.

I think the script needs to:

  1. Check for existing group membership on the discourse side, and not add people who are already in groups (or ask to remove people who aren't there)
  2. This is probably already be the case, but double-check: if fasjson is failing, log errors and do nothing.

I know David mentioned that this approach requires more API calls, but given the amount of churn the current approach seems to be causing... maybe it's a net win?


My guess is that this is related to the IPA outage problems. fasjson has had failures and some data problems which are being worked on. Until the IPA problems are settled I would expect this to occur.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Reporter (was: Needs Review)
- Issue tagged with: Needs investigation, high-gain

a year ago

We resolved https://pagure.io/fedora-infrastructure/issue/11733 and the situation should be now OK. Do you still see this happening?

Metadata Update from @dkirwan:
- Issue assigned to dkirwan

a year ago

I'm not seeing any reports of users being removed in the logs so I assume this issue is resolved now that the IPA outage is over.

I've made a minor improvement to logging and error handling around the fasjson calls inside the fas2discourse-operator, will hopefully pick up and better handle any future outages with IPA/fasjson.

Metadata Update from @dkirwan:
- Assignee reset

a year ago

Metadata Update from @dkirwan:
- Issue assigned to dkirwan

a year ago

Shall we close this now?

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

a year ago

Yeah I think we can close this now.

Sorry for lack of reply here. Got caught by FOSDEM, Council F2F, and then covid.

Are we sure this won't happen again next time there is IPA downtime?

Log in to comment on this ticket.

Metadata