#9682 Datagrepper is not logging events from the FAS account
Closed: Will Not/Can Not fix 3 years ago by smooge. Opened 3 years ago by farribeiro.

Describe what you would like us to do:

I've been told that not all actions in FAS appear in the Fedora Messaging bus and some do. But it seems that ultimately none are logged by the system, resulting in badges not being awarded for example.

One example: me and another friend fedoran we have set our timezone on the FAS (expecting to receive the white rabbit badge) but datagrepper doesn't showed that and therefore the badge wasn't awarded by none of us.

But that's not restricted only to timezone, CLA, country, security question and other fields with badges associated

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

When possible, desirable soon


We are in the midst of changing our AAA (Authentication, Authorization, Accounts) solution, you can already see the next generation at https://admin.stg.fedoraproject.org/accounts.

At this point, we will not fix anything in the current FAS and much prefer focus our efforts in the next generation.
Hopefully that one will send its notification to the message bus fine.

I enters in the link and try to update locale info, then receive 502 BAD GATEWAY and too ... that message:

Application is not available

The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

Possible reasons you are seeing this page:

    The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
    The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
    Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.

Then, that is, is out

BTW... the locale in the noggin isn't showing ... but already saved in the FAS

Metadata Update from @smooge:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

3 years ago

Staging accounts is down currently.

Metadata Update from @smooge:
- Issue status updated to: Open (was: Closed)

3 years ago

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

3 years ago

Metadata Update from @smooge:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata