Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353869 - Gerrit 2.1.8-SNAPSHOT-GerritForge-B194: Failed to obtain Gerrit configuration
Summary: Gerrit 2.1.8-SNAPSHOT-GerritForge-B194: Failed to obtain Gerrit configuration
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 0.9   Edit
Assignee: Sascha Scholz CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-04 07:20 EDT by Sascha Scholz CLA
Modified: 2012-05-21 13:16 EDT (History)
3 users (show)

See Also:

Attachments
Error log (6.70 KB, text/plain)
2011-08-04 07:20 EDT, Sascha Scholz CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Scholz CLA 2011-08-04 07:20:00 EDT 
org.eclipse.mylyn.internal.gerrit.core.client.GerritException: Failed to obtain Gerrit configuration
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritClient.refreshConfig(GerritClient.java:514)
	at org.eclipse.mylyn.internal.gerrit.core.operations.RefreshConfigRequest.execute(RefreshConfigRequest.java:30)
	at org.eclipse.mylyn.internal.gerrit.core.operations.RefreshConfigRequest.execute(RefreshConfigRequest.java:1)
	at org.eclipse.mylyn.internal.gerrit.core.operations.GerritOperation.execute(GerritOperation.java:55)
	at org.eclipse.mylyn.internal.gerrit.core.operations.GerritOperation.run(GerritOperation.java:45)
	at org.eclipse.mylyn.internal.gerrit.ui.operations.GerritOperationDialog$1.run(GerritOperationDialog.java:102)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Comment 1 Sascha Scholz CLA 2011-08-04 07:20:26 EDT 
Created attachment 200900 [details]
Error log
Comment 2 Sascha Scholz CLA 2011-09-06 04:48:10 EDT 
Cannot reproduce with Gerrit 2.1.8
Comment 3 Bruno Bossola CLA 2011-09-06 06:03:30 EDT 
As far as I can see you are trying to connect to a standard Gerrit instance. Standard Gerrit does not include TeamForge(tm) connectivity and for that reason the call is failing.

Please make sure that the gerrit endpoint you're connecting to is a valid GerritForge(tm) instance
Comment 4 Sascha Scholz CLA 2011-09-06 10:29:14 EDT 
Ups, forgot to check the error log
Comment 5 Sascha Scholz CLA 2011-09-06 17:40:16 EDT 
Fixed with 1504044f51a33103c11d2719e4bb4c54e1801956. Gerrit connector ignores unknown authentication types now.
Comment 6 Sascha Scholz CLA 2011-09-06 17:41:54 EDT 
And btw, is there a public GerritForge instance available somewhere? Where can I find the sources?
Comment 7 Steve Elsemore CLA 2012-05-14 12:10:17 EDT 
Is there any reason why when the AuthType is "TEAMFORGE", which we know will produce the error, the error could not be ignored entirely, and not logged as a warning (maybe as an option)?  Because the warning is logged, the Error Log comes to the front every time a Gerrit repository configuration is updated or a Gerrit query is synchronized, which is a bis disruptive.
Comment 8 Steffen Pingel CLA 2012-05-14 18:13:36 EDT 
I'm not sure. Please file a separate bug and attach a current error stack trace so we can consider reducing logging for an upcoming release.
Comment 9 Sascha Scholz CLA 2012-05-17 16:15:53 EDT 
I'm also not sure whether it's a good idea to ignore it completely. The better option would be to support the authentication method. We would welcome a contribution.

Are you aware of other differences in the JSON RPC communication layer between vanilla Gerrit and GerritForge?
Comment 10 Steve Elsemore CLA 2012-05-21 13:16:39 EDT 
(In reply to comment #8)
> I'm not sure. Please file a separate bug and attach a current error stack trace
> so we can consider reducing logging for an upcoming release.

Filed Bug 379489.