Closed Bug 735363 Opened 13 years ago Closed 13 years ago

Bouncer doesn't report uptake for Firefox 11.0

Categories

(Release Engineering :: Release Requests, defect)

x86_64
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

http://people.mozilla.org/~raliiev/sattap/21e3cf0f.png I checked it a couple of hours ago and it was reporting uptake around 3 for all products.
Blocks: 718778
Priority: -- → P1
... 11:52:53 <@akeybl> rail: ashughes: I'm getting "update failed" in the about dialog for 10.0.2->11 manual 11:53:20 * rail suspects bouncer 11:53:48 < joduinn> rail: on desktop OSX, doing manual check in 10.0.2, I also get "update failed" instead of 11.0 11:54:03 < joduinn> ...for manual attempt to update. just like akeybl ... 11:54:16 < rail> joduinn: filing a bug ... 11:58:11 < rail> joduinn, akeybl I disabled all updates for now ... Obviously, this blocks this morning's FF11.0.0 release.
Priority: P1 → --
QA signed off the snippets which are be served by bouncer ~15hrs ago.
This applicable to all Firefox 11.0 download links and update snippets (which are served by bouncer).
Assignee: server-ops → dgherman
The Firefox 11 files are not listed in the rsync exclude files to be synced to the mirrors.
Assignee: dgherman → nobody
Component: Server Operations → Release Engineering: Releases
QA Contact: phong → bhearsum
Assignee: nobody → rail
There were two problems here: Firefox 11 was excluded from the releases module to delete build1 bits from the mirrors. This is not normally part of our process, so cleaning this up was missed. Firefox 11 was also not added to the 'current' module. The combination of the two meant that no external mirrors could get the firefox 11 files.
Additionally, sentry was trying to check the internal mirrors and was failing due to high load of the mirrors. As a result it was removing the internal mirrors from uptake.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.