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

Bug 293873

Summary: Every modification of bug report is wrongly recognized as unsuccessful due to problems with mail settings in Bugzilla server.
Product: z_Archived Reporter: xrealine
Component: MylynAssignee: Project Inbox <mylyn-triaged>
Status: CLOSED MOVED QA Contact: Robert Elves <robert.elves>
Severity: minor    
Priority: P4 CC: robert.elves
Version: unspecifiedKeywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows Server 2003   
Whiteboard:

Description xrealine CLA 2009-11-01 11:27:37 EST
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4
Build Identifier: Eclipse 1.2.0.20090611-0950

Opening error link the extended error message appears:
Bugzilla has suffered an internal error. Please save this page and send it to ####@###.com with details of what you were doing at the time this message appeared. 
There was an error sending mail from '####@###.com' to '#####@###.com': Couldn't connect to ###.###.###.###

-----------------------------------------------

Workaround is available: 
fix mail settings or ignore wrong operation notification



Reproducible: Always

Steps to Reproduce:
Every modification of a bug report like adding a comment or attachment leads to the error message “Submit failed: a repository error has occurred.”
This happens when admin's mail account has a problem.
But in spite of the error notification, the operation was passed successfully: attachments and comments were added!
Comment 1 Denis Roy CLA 2009-11-02 08:56:16 EST
I don't understand this bug at all.
Comment 2 xrealine CLA 2009-11-03 04:39:33 EST
(In reply to comment #1)
> I don't understand this bug at all.

Steps to reproduce:

1) Connect to the local Bugzilla repository in Eclipse IDE via "Add Task Repository"
2) Open the Bugzilla's task ("Open Repository Task ...")
3) Submit a new comment (type a note in "New Comment" and press "Submit")
   The system responds: "Submit failed: A repository error has occurred..."
4) Refresh the bug report ("Synchronize Incoming Changes")
   The submitted note is there!
Comment 3 Denis Roy CLA 2009-11-03 10:04:20 EST
It appears Bugzilla cannot send you email...  Can you send me the exact details in the error message to webmaster@eclipse.org  ?

There was an error sending mail from '####@###.com' to '#####@###.com':
Couldn't connect to ###.###.###.###
Comment 4 Denis Roy CLA 2009-11-06 13:07:21 EST
After receiving details, looks like you're connecting to an internal bug repository.  That Bugzilla is unable to send mail to (someone).  Please ask your IT team for assistance, since this is not an Eclipse-related issue.
Comment 5 xrealine CLA 2009-11-17 09:45:59 EST
(In reply to comment #4)
> After receiving details, looks like you're connecting to an internal bug
> repository.  That Bugzilla is unable to send mail to (someone).  Please ask
> your IT team for assistance, since this is not an Eclipse-related issue.

Problem with sending mail is not the issue: the user doesn't need mailing notifications at all. I would agree closing this bus as a NOT_ECLIPSE if the issue is completely on server side. It means Bugzilla returns the general error for any Eclipse request.
Comment 6 Denis Roy CLA 2009-11-17 10:24:57 EST
> Problem with sending mail is not the issue: the user doesn't need mailing
> notifications at all. I would agree closing this bus as a NOT_ECLIPSE if the
> issue is completely on server side. It means Bugzilla returns the general error
> for any Eclipse request.

If you are using Eclipse Mylyn with an internal Bugzilla repository that I cannot see, and the internal Bugzilla repository that I cannot see is generating an error, how is that an Eclipse bug?
Comment 7 xrealine CLA 2009-11-18 09:01:29 EST
Before transferring the bug to Mylyn, I would like to make sure that the return code is handled correctly by Eclipse. Could you refer me to the appropriate source code?
Comment 8 xrealine CLA 2010-02-16 10:07:15 EST
The warning message in parseHtmlError()[BugzillaClient.java is confusing:
"A repository error has occurred:" and , I guess, an error core exception should not be called in this case.
Comment 9 Robert Elves CLA 2010-02-18 20:16:34 EST
This is a known issue with a few possible solutions. Please see the last few comments on bug#268207 to see if either apply to your particular situation. It would be great if you could post a comment there as well if either solution worked for you (or didn't). Thanks!

*** This bug has been marked as a duplicate of bug 268207 ***
Comment 10 xrealine CLA 2010-03-28 09:59:41 EDT
re-opened because of #293873 is different from #268207:
the bug reports a wrong notification, it's not related to any connection
failure
Comment 11 Robert Elves CLA 2010-03-29 11:39:24 EDT
comment on bug#268207: "In my particular case the local Bugzilla server was connected successfully and the attachment was uploaded. But the user is wrongly notified that the operation was failed!"

Okay so the cookie issue is not what we're seeing here then.  What language is your Bugzilla server localized to (if at all)?
Comment 12 xrealine CLA 2010-03-30 14:13:10 EDT
There is no localization - English US is installed only.

Thanks,
 Evgeny

(In reply to comment #11)
> comment on bug#268207: "In my particular case the local Bugzilla server was
> connected successfully and the attachment was uploaded. But the user is wrongly
> notified that the operation was failed!"
> 
> Okay so the cookie issue is not what we're seeing here then.  What language is
> your Bugzilla server localized to (if at all)?
Comment 13 Robert Elves CLA 2010-04-08 15:51:09 EDT
Have you been able to fix this by resolving the administrators email issue (i.e. by disabling email for the account in question)?
Comment 14 xrealine CLA 2010-05-25 08:35:01 EDT
(In reply to comment #13)
> Have you been able to fix this by resolving the administrators email issue
> (i.e. by disabling email for the account in question)?

Sometimes this workaround does not applicable. For example, when mail server is temporary down. Thus, the customer would like to have a general fix.
Comment 15 Robert Elves CLA 2010-06-24 18:01:15 EDT
Could you post a sample of the complete html error response returned when this happens?
Comment 16 xrealine CLA 2010-08-31 07:59:44 EDT
Sent by e-mail.
Comment 17 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST
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