GitLab

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

If the RING account is disabled, migration fails. The daemon log contains:

[1476376570.357|30155|ringaccount.cpp:1386    ] Account must be enabled and active to register, ignoring

Also, it takes \~30 secons after I see that log in the daemon for it to actual fail in the UI. Maybe it would be easier to just check before attempting migration if the account is dissabled and offer to enable it to perform the migration?

Afterwards, the account can be enabled in the settings, but the RingID remains blank (at least in the UI) even though the account registers.