Can't sign the CLA onreview.openstack.org

Bug #1346833 reported by Martin Borho
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Invalid
Wishlist
Unassigned

Bug Description

I want to sign the CLA but anytime there's an error message:

Code Review - Error
Server Error
Cannot store contact information

Continue

Same happens if I want to change my contact details.

Perhaps related to OpenID and Launchpad?

Revision history for this message
Martin Borho (martin-borho) wrote :
Revision history for this message
Martin Borho (martin-borho) wrote :

It works, when not entering address information, but only "I AGREE"

Revision history for this message
Jeremy Stanley (fungi) wrote :

Hopefully you're following the documentation at https://wiki.openstack.org/wiki/HowToContribute#Contributor_License_Agreement and have already joined the OpenStack Foundation by going to https://www.openstack.org/join/ ? If not, you should do that and also make sure that the Primary Email Address in your Foundation Profile at https://www.openstack.org/profile/ matches the Preferred Email in your Gerrit contact information at https://review.openstack.org/#/settings/contact .

Changed in openstack-ci:
status: New → Incomplete
Revision history for this message
Martin Borho (martin-borho) wrote :

Indeed, becoming a Openstack member first, solves this issue!

Thanks!

Clark Boylan (cboylan)
Changed in openstack-ci:
status: Incomplete → Invalid
importance: Undecided → Wishlist
Revision history for this message
Julie Pichon (jpichon) wrote :

We might want to consider making the error message more helpful (even perhaps just adding checking for Foundation membership as a suggestion, if we can't be sure why it fails?), if it is possible?

Revision history for this message
Jeremy Stanley (fungi) wrote :

I hacked the error message in our fork of Gerrit 2.4 to do that, but we don't want to run a fork any longer. To make this properly adjustable, Gerrit probably needs to be plumbed to pass the contact store API call result detail up through to the error message in the WebUI so that backends can provide arbitrary errors and differentiation between various failure modes. Right now Gerrit simply succeeds on a 200 OK response and throws one common generic failure message for any other kind of response (even other 2XX response codes).

Revision history for this message
Julie Pichon (jpichon) wrote :

Thanks for the explanation!

Revision history for this message
Lucas Ribeiro (lucasribeiro1990) wrote :

just trying to help.
I also faced this problem.
In my case I had created the gerrit account first but I didn't have created the agreement. Then I created the foundation account and after I come back to gerrit and created the agreement.
My solution was simple review and update all the gerrit information then I deleted my openstack foundation account and recreated it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.