We have identified a startup crasher for upgrades from 24.8.1. to 31.2.0 ESR please stop updates from 24.8.1 to 31.2.0 ESR
We have updates enabled from all previous 24.0 ESR versions, not just 24.8.1. I've disabled updates from all of those versions to 31.2.0. RelEng: I did this immediately with: /opt/aus2/incoming/3/Firefox for i in `ls -d 24*/*/*/*/esr`; do chmod 0 $i; done I think we need to adjust this to remove these snippets before we build 31.2.1 though, otherwise the permissions will be reset and we'll ship updates again. I'll try to come back to this today.
From release-drivers: Oh, OK. Sorry for my bad jump to conclusions! I've re-enabled updates for the other ESR versions. On Fri, Oct 17, 2014 at 09:28:41AM -0700, Benjamin Kerensa wrote: > Hi Ben, > > We only had reports of the crash impacting systems upgrading from > 24.8.1 to 31.2.0ESR. > > On Fri, Oct 17, 2014 at 9:07 AM, Ben Hearsum <email@example.com> wrote: > > Disabling the updates is done. Please note that updates to 31.2.0 are from *all* 24.0 ESR versions and not just 24.8.1. I've disabled updates from all of these versions. > > So, we only need to remove the 24.8.1 esr snippets.
OK, I removed the 24.8.1 snippets with: rm -rf 24.8.1/*/*/*/esr So there's nothing left to do here. The test snippets will get updated when we built 31.2.1, and new live updates will be made available when we ship.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
More updates from r-d: David and Ben, I just spoke with Lukas and our understanding was only 24.8.1 is updating to 31.2.0. If the other 24 ESR releases are updating to 31.2.0 then they should be disabled. Thanks, -- I ran this to disable updates for all of the other 24 ESR versions: cd /opt/aus2/incoming/3/Firefox rm -rf 24*/*/*/*/esr
Summary: Stop Updates for 24.8.1 ESR to 31.2.0 ESR → Stop Updates for 24.* ESR to 31.2.0 ESR
I've verified that all 24.x.x ESR branches no longer update to 31.2.0 on the live esr channel. I've also verified that 31.1.1 ESR does successfully update to 31.2.0, as above. If this is the desired behavior, consider this bug verified. If not, please get in touch.
verified. For archiving purpose, could you put the bug which leaded us to take this action?
Status: RESOLVED → VERIFIED
Yes that would be bug #1055766 and we now have a repro and have someone working on a fix for that.
You need to log in before you can comment on or make changes to this bug.