Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-critical error after sync #10

Open
frafra opened this issue Jun 24, 2019 · 5 comments
Open

Non-critical error after sync #10

frafra opened this issue Jun 24, 2019 · 5 comments
Assignees
Labels
bug Something isn't working need info Extra information is required

Comments

@frafra
Copy link

frafra commented Jun 24, 2019

[error] Gitlab failure: "namespace.route" can't be blank, "notification_email" can't be blank, "notification_email" is invalid
@Adambean
Copy link
Owner

I guess this is for new users being created?
Which version of Gitlab are you running? (I've not tried this tool on 12 yet.)

@Adambean Adambean added the bug Something isn't working label Jun 24, 2019
@Adambean Adambean self-assigned this Jun 24, 2019
@frafra
Copy link
Author

frafra commented Jun 25, 2019

Yes, it happens after users creation. I am testing it with GitLab 12.

@Adambean
Copy link
Owner

I just ran this against our updated Gitlab 12 instances today. A single new user needed to be created, and did so without any problems.

Are you certain there are valid email addresses assigned to your LDAP users, and that this tool is reading them? If it encounters a user with a non-empty but invalidly formatted email address that could cause it, so if it only happens with one user I'd inspect their object attributes to ensure they're valid.

@Adambean Adambean added the need info Extra information is required label Jul 6, 2019
@beharbunjaku
Copy link
Contributor

beharbunjaku commented Jul 31, 2019

This error occurred to me as well. In my case it was the "ghost" user from gitlab that was causing it.
Try adding userNamesToIgnore: ["ghost"]. If it is not that, check the API logs.
I think, this tool should ignore the "ghost" user by default, just as it does with the "root" user.

beharbunjaku added a commit to beharbunjaku/gitlab-ce-ldap-sync that referenced this issue Jul 31, 2019
…essage "namespace.route" can't be blank...)
Adambean added a commit that referenced this issue Jul 31, 2019
#10 ignore build-in ghost user by default
@Adambean
Copy link
Owner

@beharbunjaku's change has been merged in if you'd like to try it out @frafra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working need info Extra information is required
Projects
None yet
Development

No branches or pull requests

3 participants