Community
Participate
Working Groups
The bugzilla connector seems to not work with https://bugs.eclipse.org/bugs. If you create a new repo, refreshing the config fails and you can't create useful queries. If you do create a query, it retrieves tasks but fails to open them. In workspaces that already have the repo config from before, queries work fine. I tested the connector with https://landfill.bugzilla.org/bugzilla-5.0-branch/ and there were no problems so this seems to be specific to https://bugs.eclipse.org/bugs/.
Sam, I run successful the unit tests for http://mylyn.org/bugzilla-5.0.3/ and http://localhost:2080/bugzilla-rest-5.0.3/. Next step is to look where we fail in https://bugs.eclipse.org/bugs
We get the error in org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.getBugzillaLoginTokenIfExists(IProgressMonitor) javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
This may be a side effect of 527549. We've re-enabled TLSv1.0, but I'll bet there's cipher issue. I've turned on some 'weaker' ciphers so let me know if that fixes this. If it does we'll need to work out which cipher you actually need so I can disable the rest. -M.
(In reply to comment #3) > This may be a side effect of 527549. We've re-enabled TLSv1.0, but I'll bet > there's cipher issue. I've turned on some 'weaker' ciphers so let me know if > that fixes this. If it does we'll need to work out which cipher you actually > need so I can disable the rest. > > -M. Yes, now I can connect to https://bugs.eclipse.org/bugs.
(In reply to comment #3) > This may be a side effect of 527549. We've re-enabled TLSv1.0, but I'll bet > there's cipher issue. I've turned on some 'weaker' ciphers so let me know if > that fixes this. If it does we'll need to work out which cipher you actually > need so I can disable the rest. > > -M. If you can tell me what steps you did when you disable TLSv1.0 and what ciphers get turned off I can try to chang my local test environment and prepers a fix so that mylyn bugzilla connector no longer need TLSv1.0. Or is it possible that you can only configure that https://bugs.eclipse.org/bugstest use your new settings?
(In reply to Frank Becker from comment #5) > If you can tell me what steps you did when you disable TLSv1.0 We simply removed TLS1.0 from the list of supported protocols on the webserver. Since this has caused a little chaos externally and internally we've turned it back on for now. > ciphers get turned off I can try to chang my local test environment and > prepers a fix so that mylyn bugzilla connector no longer need TLSv1.0. We had turned off any AES128(most of which seem to be SSLv3) ciphers, but Java seems to like them so for now we've turned them on. >Or is it possible that you can only configure that https://bugs.eclipse.org >/bugstest use your new settings? No, bugstest is served by the same hosts as the main instance, so it's sort of all or nothing. -M.
New Gerrit change created: https://git.eclipse.org/r/112753
Anything else I can do here? -M.
(In reply to Eclipse Webmaster from comment #8) > Anything else I can do here? > > -M. Maybe someone can help my with the following problem. For a Fix I need to merge some gerrit reviews for the needed changes of the local test environment. But the build for review https://git.eclipse.org/r/112753 Hudson job https://hudson.eclipse.org/mylyn/job/gerrit-mylyn-commons/428/ fails and I have no idea how to solve the org.osgi.framework.BundleException error (see https://hudson.eclipse.org/mylyn/view/Gerrit/job/gerrit-mylyn-commons/ws/org.eclipse.mylyn.commons.tests/target/work/configuration/1513626063219.log/*view*/).
Fred or Mikael, can you offer any insight? -M.
I guess other Mylyn committers could help here, as Frank's change does not touch anything beside a java file. Adding Sam to cc list.
(In reply to Mikaël Barbero from comment #11) > I guess other Mylyn committers could help here, as Frank's change does not > touch anything beside a java file. Adding Sam to cc list. I think I have narrowed down the problem. I create review https://git.eclipse.org/r/115411
I guess this one can be marked as resolved?
No this was not really fixed. We need a fix in mylyn and not by enable the removed TLS1.0
I can not reproduce this with my test environment. I need the list of enabled ciphers so that i can compare this with my local apache2 settings.
Frank, are you saying the connector does not support repositories that don't have TLS1.0 enabled? If so, please update the summary of this bug accordingly.
This https://stackoverflow.com/questions/53146096/has-anyone-succeeded-in-getting-eclipses-report-bug-or-enhancement-to-work suggests my https://bugs.eclipse.org/bugs/show_bug.cgi?id=540761 may be related.
*** Bug 540761 has been marked as a duplicate of this bug. ***
Evidently 540761 is not a /duplicate/. 540761 says "Unexpected error while creating task for error report" and this doesn't. All that can be deduced from your evidence is that they two may be causally related.
I can not setup my test environment so that I can reproduce this. If someone has a test instance that I can access then I can continue on the Mylyn side.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
