723182 - Force correlation reports for current in-development Firefox versions, clean up old forced versions

Status: VERIFIED FIXED

(Socorro :: Backend, task)

Description

[Robert Kaiser]

https://github.com/mozilla/socorro/blob/master/scripts/crons/cron_libraries.sh forces correlation reports for the three most-crashing Firefox betas and two extra ones in addition. We should change that to force the current in-development versions instead.

I'll try to do a patch for this myself.

Comment 1

[Robert Kaiser]

And I hope I did it correctly: https://github.com/mozilla/socorro/pull/313

Comment 2

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/5d1848e969d8349d2a1f9cca6fb7ceea4849d676
Fixes bug 723182 - Force correlation reports for current in-development Firefox versions, clean up old forced versions

Comment 3

[Robert Helmer [:rhelmer]]

Added a note to https://wiki.mozilla.org/Socorro:Releases/2.4.2 that we need to modify the crontab for this to take effect.

Comment 5

[Robert Helmer [:rhelmer]]

Something I overlooked here - the admin box needs to explicitly inherit the monitor config, since in production there are multiple network routes to get to hbase.

It's a one-line fix, here's the pull req: https://github.com/mozilla/socorro/pull/360

Comment 6

[[github robot]]

Commits pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/6062f224309f6e0e162aa2ff9ed20212f4b60a49
bug 723182 - pull in monitor config, to get the correct hbaseHost for the admin box

https://github.com/mozilla/socorro/commit/ff9ab124e8720069bf9458e67ca576b7a164ec2f
Merge pull request #360 from rhelmer/bug723182-missing-config

fixes bug 723182 - pull in monitor config, to get the correct hbaseHost for th...

Comment 7

[Robert Helmer [:rhelmer]]

Merged to master branch, but we need to get this deployed still.

Comment 8

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #7)
> Merged to master branch, but we need to get this deployed still.

I am going to modify the crontab to point to the old version, and we can ship this fix with 2.4.3 (next Wed.)

Comment 9

[Robert Helmer [:rhelmer]]

Backed out crontab to previous rev in puppet (r27086):
Committed revision 28898.

Comment 10

[Robert Helmer [:rhelmer]]

Jason is running the pre-2.4.2 script on prod now, so we'll get reports for today (http://rhelmer.pastebin.mozilla.org/1485604).

It should be done in the next few hours, and we'll get the new version out for 2.4.3

Sorry for the hassle!

Comment 11

[Scoobidiver (away)]

Thanks for your reactivity!

Comment 12

[Laura Thomson :laura]

I don't think we shipped the crontab changes in 2.4.3 as this is still no happening.  Re-opening

Comment 13

[Laura Thomson :laura]

rhelmer: can we do this out of band for a release?  or does it need to wait for 2.4.4?

Comment 14

[Robert Helmer [:rhelmer]]

(In reply to Laura Thomson :laura from comment #13)
> rhelmer: can we do this out of band for a release?  or does it need to wait
> for 2.4.4?

We can make the crontab changes anytime, as long as the proper script was shipped. I can do so today.

Comment 15

[Robert Kaiser]

(In reply to Robert Helmer [:rhelmer] from comment #14)
> We can make the crontab changes anytime, as long as the proper script was
> shipped. I can do so today.

That would be great!

Comment 16

[Robert Helmer [:rhelmer]]

Crontab changes checked in (r29519)

This should work on tomorrow's run, let's reopen again and get it fixed on Wednesday if not (based on my manual testing on prod I do expect it to work)

Comment 18

[Scoobidiver (away)]

Verified in https://crash-analysis.mozilla.com/crash_analysis/20120228/:
There are correlation reports for 9.0.1, 10.0.2, 11.0, 12.0a2, 13.0a1 and crash signatures that have more than 10 crashes/day.

Nevertheless, they are not displayed in the Correlations tab (bug 715969?).