Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321991

Summary:	Bugzilla connector says "unable to login"
Product:	z_Archived	Reporter:	Nikolay Antipov <nick.antipov>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, robert.elves
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Nikolay Antipov

2010-08-06 10:26:24 EDT

Build Identifier: 20100218-1602

Server is http://sam-it-svn.megafonvolga.ru:8333/bugzilla
bugzilla 3.6.1

When I press "Validate Settings" error appears on the top of window: " Unable to login to http://sam-it-svn.megafonvolga.ru:8333/bugzilla."

Username/password are specified, anonymous login doesn't solve this problem.

I've checked the logs of apache where bugzilla runs, but it nothing contains about bugzilla. It looks like connector event didn't try to connect.

ping sam-it-svn.megafonvolga.ru successfully works,
and I can reach bugzilla over browser without any problems.

Eclipse doesn't write any logs about this problem. I can't diagnostic this problem.

Thanks.

Reproducible: Always

Steps to Reproduce:
1.open task repositories view;
2.choose my repository, double click;
3.press "Validate Settings".

Comment 1 Steffen Pingel

2010-08-18 02:54:51 EDT

Are you using any kind of proxy?

Comment 2 Nikolay Antipov

2010-08-19 01:29:05 EDT

(In reply to comment #1)
> Are you using any kind of proxy?

No, I'm not.

Comment 3 Nikolay Antipov

2010-08-19 02:44:25 EDT

I've specified a version of org.eclipse.mylyn.bugzilla_feature.
Full version number is 3.3.3.v20100330-0100-e3x.

Comment 4 Steffen Pingel

2010-08-19 04:21:09 EDT

Would you be able to try the latest 3.4.1 release of Mylyn?

Comment 5 Nikolay Antipov

2010-08-19 07:27:54 EDT

(In reply to comment #4)
> Would you be able to try the latest 3.4.1 release of Mylyn?

I've updated to mylyn 3.4 (and restarted eclipse), but problem still happens.
Default bugzilla configuration for eclipse.org doesn't work too (the same reason).

May be this is my specific problem. May be is there a special method to debug this problem (logs, special debug keys, etc.)?

Comment 6 Nikolay Antipov

2010-08-19 07:57:09 EDT

Additional information.

Problem didn't appear when use ip-address instead hostname.

But for bugs.eclipse.org -> 206.191.52.46 this solution didn't work.

Comment 7 Steffen Pingel

2010-08-19 14:18:28 EDT

Rob, Frank, could that be related to the cookie domain problem? Not sure which bug this was.

Comment 8 Frank Becker

2010-08-21 16:04:42 EDT

(In reply to comment #7)
> Rob, Frank, could that be related to the cookie domain problem? Not sure which
> bug this was.

This was bug# 268207. Yes that could be an cookiedomain problem.
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=268207#c52)

Comment 9 Steffen Pingel

2010-08-21 16:53:32 EDT

Nikolay, can you check if bug 268207 applies to your environment?

Comment 10 Nikolay Antipov

2010-08-23 01:40:07 EDT

(In reply to comment #9)
> Nikolay, can you check if bug 268207 applies to your environment?

My bugzilla has a parameter cookiepath, which was incorrectly set. I've changed this parameter and changed ip address to hostname and now I can't reproduce an error.

I made a mistake in parameter cookiepath one more time, but problem still doesn't appear.

And most interesting thing, https://bugs.eclipse.org/bugs now works, although I can't change any parameter at eclipse's bugzilla host.

So, what we have. Bug disappeared, but I can't completely answer why did it happen.

I think we can close this bug as RESOLVED. In case of bug repeat I open one more bug with more detail information.

What do you think?

Thanks a lot!

Comment 11 Steffen Pingel

2010-08-23 12:02:35 EDT

Thanks for verifying. Marking resolved.