Bug 1434579 - gerrit requires inappropriate write permissions!!!
Summary: gerrit requires inappropriate write permissions!!!
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-21 20:21 UTC by James (purpleidea)
Modified: 2017-05-21 03:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-21 03:51:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
screenshot (35.96 KB, image/png)
2017-03-21 20:21 UTC, James (purpleidea)
no flags Details

Description James (purpleidea) 2017-03-21 20:21:19 UTC
Created attachment 1265195 [details]
screenshot

Description of problem:

Try to login with GH account from gerrit. It asks for write permissions to repos! Not okay for new contributors!

See screenshot for details.

Comment 1 Nigel Babu 2017-03-22 03:07:47 UTC
This is most likely a relic of the Gerrit upgrade and subsequent problems with the Github plugin. Could you check if https://gerrit-stage.rht.gluster.org/ works correctly?

It works for me, but I'm curious if you can login correctly (and thus your user is created).

This will need to wait for a bit since it needs a Gerrit down time to fix.

Comment 2 James (purpleidea) 2017-03-29 21:08:16 UTC
Hey Nigel,

Sorry for the delay in my response. I tried that and it's the same issue for that site too.

Thanks,
James

Comment 3 Nigel Babu 2017-03-30 01:16:10 UTC
Ah, apologies. I was testing out Ansible changes for Gerrit on staging yesterday and most likely overwrote the config file with the older version. Can you test it now? I've made the change in Ansible.

Comment 4 Nigel Babu 2017-05-21 03:51:00 UTC
This is fixed already.


Note You need to log in before you can comment on or make changes to this bug.