Hello! I am trying to register a new fedora account but I am stuck on step 3. After choosing a password, I am prompted "Something went wrong while creating your account, please try again later." Result is the same even later on.
I think that what could be happening is the following: - I created such new account a few days ago, received the activation email, but then I forgot. - After the activation email token expired, I requested a new one through the link provided i the email. - Following the new activation token, I could continue the registration procedure, but now it's stuck on step 3.
Not sure if you can reproduce, let me know if you need any more details!
Hopefully soon.
<img alt="Screenshot_from_2021-07-26_15-51-53.png" src="/fedora-infrastructure/issue/raw/files/7ea5cf9466c5ea381f5af7fc47e2abaa53a8bb094470a94e4035cc6cccc9feee-Screenshot_from_2021-07-26_15-51-53.png" />
There is an issue with creating new accounts at the moment. IPA is returning an error:
IPA Error 4203: DatabaseError Operations error: Allocation of a new value for range cn=posix ids,cn=distributed numeric assignment plugin,cn=plugins,cn=config failed! Unable to proceed.
I am looking into it and will update here
This issue should be fixed now, we had set a restrictive id range which has now been extended which will allow new users to create accounts.
Let me know if there is any further difficulty
Metadata Update from @mobrien: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
It seems something (but not ansible?) is reverting this fix...
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
@kevin do you mean the "range size" which is actually set to 200000 ?
I have no idea... @mobrien was working on it, so I am not sure what he changed.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: high-gain, medium-trouble, ops
Yes, the overall id range is set to 200000 but within that there is a dna range which is a subset of those assigned to each replica so that no overlapping occurs between replicas. These should automatically adjust as necessary when a new id is needed provided that there are more ids available in the overall id range. There is an option to set these ranges manually which we don't use. I updated the range manually to temporarily fix this problem but the automatic reassigning broke that fix.
It appears to all be working again now though, my best guess is there was a break down in communication between the replicas but I am not sure to be honest.
However it does appear to be working correctly again.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.