ESR version locked to 60.9 ESR if updating from releases before it
Categories
(Release Engineering :: Release Automation: Updates, defect)
Tracking
(firefox-esr6871+ verified)
People
(Reporter: cfogel, Assigned: jcristau)
Details
Attachments
(3 files)
Affected versions
- ESR builds up to 60.9ESR;
Affected platforms
- Windows 10, macOS 10.15, Ubuntu 18.04;
Steps to reproduce
- set the update chanel to esr-localtest
- Launch Firefox;
- Start the Update process from the Help menu;
- Press the Ok button once available;
- Restart the browser;
- Check the browser version;
Expected result
- update to 68.3.0-build2 is successfully completed;
Actual result
- browser updates to 60.9 restarting the update process doesn't continue the update to the expected version;
Regression range
- updates for ESR-68.2.0 worked as expected, results for the testing session can be found in this document;
Additional notes
- attempted the update process with 52.9.0esr(RU) .exe on Win10 and after 2 seconds of "applying updates" the pop-up for manually installing Firefox was displayed instead;
- with 52.0 esr(ja) .tar.bz2 on Linux the update was locked to 60.9esr;
- with 60.0.2esr(ar) .zip on Win10 the update was up to 60.9esr but the language got changed to english;
- for additional info, contact either me or :csasca.
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Please attach the log from the failed update.
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
BTW a step through 60.9 is expected for on all platforms when updating from 52.x, and on windows regardless. But that should then update to 68.3.
Reporter | ||
Comment 3•4 years ago
|
||
Attached is the log, updated from 60.8.0esr - Win10
Reporter | ||
Comment 4•4 years ago
|
||
@Julien, Firefox is marked as up to date.
Assignee | ||
Comment 5•4 years ago
|
||
Deleted the esr60 rules on esr-localtest and esr-cdntest, we should be good now.
Comment 6•4 years ago
|
||
Here's the 52.9.0's update log.
Assignee | ||
Comment 7•4 years ago
|
||
The error from comment 6 is because the bz2 watershed rule on esr has priority 125, but only 65 on esr-localtest, so it's overridden by the windows 60.9 watershed. esr-cdntest is likewise broken.
Assignee | ||
Comment 8•4 years ago
|
||
Updated the esr52-localtest and esr52-cdntest rules to have priority 125.
Reporter | ||
Comment 9•4 years ago
|
||
Marking as verified since they appear to work ok now.
Thanks again for the help!
Description
•