Closed Bug 1600046 Opened 4 years ago Closed 4 years ago

ESR version locked to 60.9 ESR if updating from releases before it

Categories

(Release Engineering :: Release Automation: Updates, defect)

defect
Not set
blocker

Tracking

(firefox-esr6871+ verified)

VERIFIED FIXED
Tracking Status
firefox-esr68 71+ 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
  1. Launch Firefox;
  2. Start the Update process from the Help menu;
  3. Press the Ok button once available;
  4. Restart the browser;
  5. 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.
Summary: Version to 60.9 ESR if updating from releases before it → ESR version locked to 60.9 ESR if updating from releases before it

Please attach the log from the failed update.

Flags: needinfo?(cristian.fogel)

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.

Attached file updateTO609.txt

Attached is the log, updated from 60.8.0esr - Win10

Flags: needinfo?(cristian.fogel)
Attached image Screenshot_1.png

@Julien, Firefox is marked as up to date.

Deleted the esr60 rules on esr-localtest and esr-cdntest, we should be good now.

Assignee: nobody → jcristau
Status: NEW → RESOLVED
Closed: 4 years ago
Component: Application Update → Release Automation: Updates
Product: Toolkit → Release Engineering
QA Contact: mtabara
Resolution: --- → FIXED
Version: 68 Branch → unspecified
Attached file 52.9.0ru.txt

Here's the 52.9.0's update log.

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.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated the esr52-localtest and esr52-cdntest rules to have priority 125.

Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED

Marking as verified since they appear to work ok now.
Thanks again for the help!

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.