You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgraded to 5.10.0 recently in our production system and this service refused to launch, because we had removed the bootstrap superadmin user. I would have expected the service to skip past the superadmin password initialiser and continue to launch, rather than crash.
The text was updated successfully, but these errors were encountered:
Hey, we just ran into this issue after upgrading from v5.7.2 to v5.10.0. The service-authorization container keeps restarting and throws an EntityNotFoundException exception:
We managed to use the same workaround and manually created the superadmin user in the database:
docker compose exec -it postgres psql -U rpuser reportportal
\dt
\d users
SELECT * FROM users WHERE login LIKE 'superadmin';
(0 rows)
INSERT INTO users (login, email, role, type, expired)
VALUES (‘superadmin’, ‘[email protected]’, ‘USER’, ‘INTERNAL’, FALSE);
SELECT * FROM users WHERE login LIKE 'superadmin';
(1 row)
Afterwards the service was able to start without any issues and we were able to log in again.
I think the AdminPasswordInitializer should be updated to allow the absence of the superadmin user - because some deployments might want to remove it in favour of personalized admin accounts.
Upgraded to 5.10.0 recently in our production system and this service refused to launch, because we had removed the bootstrap
superadmin
user. I would have expected the service to skip past the superadmin password initialiser and continue to launch, rather than crash.The text was updated successfully, but these errors were encountered: