I have etckeeper set up on our machines at work, and etckeeper is configured to push to our Gitlab CE instance. This has been working for a few years.
I upgraded to 8.15 (and now to 8.15.2, which changed the error message), and now pushes error out:
# git push metrics GitLab: The project you were looking for could not be found. fatal: The remote end hung up unexpectedly
If I go in to the admin area and impersonate the machine’s user (and do absolutely nothing else—just impersonate, then immediately stop impersonating) it fixes it. But there are 30 to 40 of them…
So, looking for what might be causing this—and a less tedious way to fix it.
(Some extra details: these are all local accounts that were created with the API. They are confirmed. We also have LDAP accounts, these do not have any LDAP identities associated.)
Comparing a user (in the database
users table) before and after impersonating:
-sign_in_count | 0 -current_sign_in_at | -last_sign_in_at | -current_sign_in_ip | -last_sign_in_ip | +sign_in_count | 1 +current_sign_in_at | 2016-12-31 18:00:27.743992 +last_sign_in_at | 2016-12-31 18:00:27.743992 +current_sign_in_ip | 172.16.15.10 +last_sign_in_ip | 172.16.15.10 @@ -14 +14 @@ -updated_at | 2016-12-31 18:00:11.721347 +updated_at | 2016-12-31 18:00:27.745426 @@ -62 +62 @@ -authorized_projects_populated | +authorized_projects_populated | t
Only thing that looks at all interesting is
Indeed appears there is a
project_authorizations table that is only populated on web login. There must be some other way to populate this; did some migration get skipped or something?