814511 - Saving a campaign returns an error "Something bad happened. It's not you, it's me."

Status: RESOLVED INVALID

(Socorro :: General, task)

Description

[Mark Banner (:standard8)]

Saving a campaign returns an error:

=======
Error

Something bad happened. It's not you, it's me.

Please file an issue in Bugzilla describing what happened, and please include the URL for this page.
=======

The url is http://crash-stats.mozilla.com/admin/save_campaign

The campaign is added to the list, but I've no idea if it has been successfully sent out or not.

Comment 1

[Mark Banner (:standard8)]

AFAICT email campaigns just aren't working - I did one yesterday that I believe should have included a crash that I submitted yesterday, but I've not received an email (I also did one a little while ago and not got email from that).

Comment 2

[Robert Helmer [:rhelmer]]

Same as https://bugzilla.mozilla.org/show_bug.cgi?id=814512#c1 I think:

"Pretty sure this is a dup of 650428

Also, this feature is deprecated and being replaced with bug 814647"

Comment 3

[Mark Banner (:standard8)]

Bug 650428 seems slightly different - in that the email campaign is sent off. I've no proof here that it did / didn't send off any emails - I had also submitted a crash with my email, and I've not received an email.

(In reply to Robert Helmer [:rhelmer] from comment #2)
> Also, this feature is deprecated and being replaced with bug 814647

So bug 814647 doesn't seem to cover the same..., but I'll comment there.

Comment 4

[Wayne Mery (:wsmwk)]

> (In reply to Robert Helmer [:rhelmer] from comment #2)
> > Also, this feature is deprecated and being replaced with bug 814647
> 
> So bug 814647 doesn't seem to cover the same..., but I'll comment there.

Thunderbird is not sufficiently helped by bug 814647

I just attempted to send to PL_HashTableRawRemove | PL_HashTableRemove | nsNodeInfoManager::RemoveNodeInfo(nsNodeInfo*) for several versions of Thunderbird and it claimed it would send to ~523 users.  But I still get this error.  

So can't communicate to users who are crashing. Unless this is actually working but is reporting as failed?

Comment 5

[Robert Helmer [:rhelmer]]

(In reply to Wayne Mery (:wsmwk) from comment #4)
> > (In reply to Robert Helmer [:rhelmer] from comment #2)
> > > Also, this feature is deprecated and being replaced with bug 814647
> > 
> > So bug 814647 doesn't seem to cover the same..., but I'll comment there.
> 
> Thunderbird is not sufficiently helped by bug 814647
> 
> I just attempted to send to PL_HashTableRawRemove | PL_HashTableRemove |
> nsNodeInfoManager::RemoveNodeInfo(nsNodeInfo*) for several versions of
> Thunderbird and it claimed it would send to ~523 users.  But I still get
> this error.  
> 
> So can't communicate to users who are crashing. Unless this is actually
> working but is reporting as failed?

I don't think this feature works at all anymore. Adrian, should we remove it now that bug 814647 has landed?

If bug 814647 doesn't precisely cover the use case, we should figure that out. In the meantime, you can file a bug in Socorro::Data Requests to get this done (either to get a list of email addresses, or to ask someone to send this) since the current feature was supposed to be disabled and it just hasn't been removed yet.

Comment 6

[[DEACTIVATED] Adrian Gaudebert]

I don't know if that feature should be removed or not (my guess would be not as it is useful to some people), but it has not been working for quite a long time now, and we haven't spent any time into maintaining it. 

Current state is: 
 * the middleware service is old and depreciated, and will disappear once we move to the configmanized middleware
 * the email campaign feature does not exist in the new django WebApp
 * we send automatic emails to Firefox users _only_

The main question is: do we want that feature is Socorro? 

Laura, KaiRo, Cheng, what do you think?

Comment 7

[Robert Kaiser]

This really needs Cheng's input, as IIRC this was primarily made for his team. I never used this feature.

Comment 8

[[DEACTIVATED] Adrian Gaudebert]

This doesn't exist anymore in both the middleware and the django UI. We heard no complaints about it. Let's mark this as invalid.