1177917 - update.xml empty for nightly, build not updating while there are newer builds on the ftp server

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Pascal Chevrel:pascalc (PTO until April 26)]

My Nightly didn't update in the last 2 days:
Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 ID:20150624080416 CSet: 4cdc1a95a672

I see more recent nightly builds on the FTP server:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/


The update file that firefox is querying is empty, so it doesn't install the update:
view-source:https://aus4.mozilla.org/update/3/Firefox/41.0a1/20150624080416/Linux_x86_64-gcc3/fr/nightly/Linux%203.19.0-21-generic%20%28GTK%202.24.27%29/default/default/update.xml?force=1

Comment 1

[Sylvestre Ledru [:Sylvestre]]

Rail, Nick, can you help on this?
This can probably wait a few days if you have other things in mind. ;)

Comment 2

[Rail Aliiev [:rail]]

L10n was broken by https://bugzilla.mozilla.org/show_bug.cgi?id=1174241#c6

The fix has been landed and I retriggered m-c and m-a l10n repacks.

I'll keep an eye on this.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

My bug 1178992 has been marked as duplicate of this bug. It is somewhat a blocker for us given that we do not receive any pulse notificatoin for repacks for both nightly and aurora. 

Can we give that bug a higher priority because we really want to continue testing localized builds with our Firefox UI Tests.

Comment 5

[Rail Aliiev [:rail]]

This bug is actually resolved.

Regarding the pulse notifications. You should be receiving. I suspect that your routing key still uses the old pattern (build.{branch}-{platform}-l10n-nightly.*.finished). After we switched to mozharness based l10n repacks and started using chunks, the patterns look like these:

build.{branch}-{platform}-l10n-nightly-1.*.finished
build.{branch}-{platform}-l10n-nightly-2.*.finished
build.{branch}-{platform}-l10n-nightly-3.*.finished
build.{branch}-{platform}-l10n-nightly-4.*.finished
build.{branch}-{platform}-l10n-nightly-5.*.finished
build.{branch}-{platform}-l10n-nightly-6.*.finished
build.{branch}-{platform}-l10n-nightly-7.*.finished
build.{branch}-{platform}-l10n-nightly-8.*.finished
build.{branch}-{platform}-l10n-nightly-9.*.finished
build.{branch}-{platform}-l10n-nightly-10.*.finished

They are not ideal, I'd really like to change them so we can have better AMQP pattern matching. :/

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Rail Aliiev [:rail] PTO Aug 7-12 from comment #5)
> Regarding the pulse notifications. You should be receiving. I suspect that
> your routing key still uses the old pattern
> (build.{branch}-{platform}-l10n-nightly.*.finished). After we switched to
> mozharness based l10n repacks and started using chunks, the patterns look
> like these:

Thanks. That's indeed the issue here as it looks like. Regarding this routing key change, was there somewhere an announcement? I have seen so many changes lately (across projects) where the API gets changed but customers are not getting informed about. :( Maybe I simply miss an email to a mailing list?

Anyway I will file a new bug to get the problem fixed in pulsetranslator.