EasyCLA not authorizing previously signed ECLA

[jarias-lfx]

Summary

Received reports of previously authorized contributors (ECLA) not passing EasyCLA. Confirmed the ECLA correctly in the DB.
For some projects the Oauth is failing with a 502 error message:

The <Corporate or Individual> CLA option is not enabled for this project. Please contact to your administrator to enable the Corporate CLA option for this project.

Background

There was a release today Wednesday March 5th 2025. After the release GitHub ECLA users are not getting the authorization.

Affected PRs:
open-telemetry/opentelemetry-dotnet-contrib#2631
open-telemetry/opentelemetry-collector-releases#858
ttps://github.com/pytorch/pytorch/pull/145021#issuecomment-2597164046
pytorch/pytorch#148597 (comment)
pytorch/pytorch#148596 (comment)
pytorch/pytorch#148593 (comment)
pytorch/pytorch#148592 (comment)
AcademySoftwareFoundation/OpenRV#708

Expected behavior

EasyCLA should pass

[breedx-splk]

Probably plenty of examples above, but here's another: open-telemetry/opentelemetry-android#870

[jenrik]

Following is also affected: open-telemetry/opentelemetry-helm-charts#1560

[jarias-lfx]

Update:

• One of the issues (Getting 502) during the oauth process has been resolved.
• We are still investigating the issue with the CCLA contributor acknowledgements not being handled correctly.

[Kielek]

@jarias-lfx, do you have any ETA for the fix?

[lukaszgryglicki]

Should be now fixed.

[jarias-lfx]

502 Error is still visible on FinOps-Open-Cost-and-Usage-Spec/EasyCLA#290