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

Getting 502 during CCLA flow for Gerrit #4273

Closed
2 of 15 tasks
jarias-lfx opened this issue Mar 14, 2024 · 3 comments
Closed
2 of 15 tasks

Getting 502 during CCLA flow for Gerrit #4273

jarias-lfx opened this issue Mar 14, 2024 · 3 comments
Assignees
Labels
01 - High High Priority bug Something isn't working

Comments

@jarias-lfx
Copy link

Summary

Executing an ECLA (Acknowledgement) process for Gerrit, the user is getting a 502 error and is unable to process.

Background

Steps:
1- Access project GerriT:
2- Select Configuration.
3- Select agreements.
4- Select new contributor agreement.
5- Select CCLA.
6- Select Please review the agreement.
7- Select Proceed to Corporate Authorization.
8- Search for the organization.
9- Select the organization and select proceed.
10- The user is unable to process.

Expected behavior

The contributor should be prompted with the acknowledgement confirmation and be added to the CCLA LDAP group.

Screenshots

Error:
image
image

Environment

  • Environment:
    • ALL
    • DEV
    • STAGING
    • PROD
  • Browser:
    • Chrome/Brave
    • Firefox
    • Opera
    • Vivaldi
    • LibreWolf
    • SRware Iron
    • Dissenter
    • Slimjet
    • Midori
    • Edge
    • Lynx
@jarias-lfx jarias-lfx added bug Something isn't working 01 - High High Priority labels Mar 14, 2024
nickmango added a commit to nickmango/easycla that referenced this issue Mar 25, 2024
- Resolved signature update for the gerrit employee signature update

Signed-off-by: Harold Wanyama <[email protected]>
nickmango added a commit that referenced this issue Mar 25, 2024
@mlehotskylf
Copy link
Contributor

This is fixed so moving to QA.

@thakurveerendras
Copy link
Contributor

Unable to replicate the same issue on the dev site, So updating this issue status.

image

@thakurveerendras
Copy link
Contributor

Closing this ticket as it is working fine prod, Confirmed by jarias-lfx over the slack
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 - High High Priority bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants