Closed
Bug 1298503
Opened 8 years ago
Closed 8 years ago
Serve 48.0.2 updates to Windows users with "(nowebsense)" in update URL
Categories
(Release Engineering :: Release Requests, defect, P1)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ddurst, Assigned: Callek)
References
(Blocks 1 open bug)
Details
Currently, Windows (32bit or 64bit) users who have WebSense installed will encounter a startup crash if they update to 48 (bug 1294650).
To mitigate this, a hotfix has been developed (bug 1298404) to indicate the presence of WebSense as best we can detect, for clients running Firefox 39-47 on Windows. This hotfix will change the app.update.pref url to be: https://aus5.mozilla.org/update/6/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%(XXX)/%SYSTEM_CAPABILITIES%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
where (XXX) will be either (websense) or (nowebsense).
(websense) should only be permitted to update to 47.0.x.
(nowebsense) should be permitted to update to 48.x.
Reporter | ||
Updated•8 years ago
|
Summary: Adjust update target for Windows clients < 47 based on presence or absence of WebSense → Adjust update target for Windows clients on 39-47 (inclusive) based on presence or absence of WebSense
Comment 1•8 years ago
|
||
As said in bug 1298404, this should not go live today. We need to have QE signing off this.
Comment 2•8 years ago
|
||
My expectation is that Jordan will be taking care of this. Feel free to re-assign if that's wrong.
Component: Balrog: Backend → Releases
QA Contact: bhearsum → rail
Comment 3•8 years ago
|
||
14:39:18 <jlund> lizzard: heya :) - re: bug 1298503, where do we stand? do you know if this is still required and what the ETA is that it will used?
15:13:49 <lizzard> jlund: Sylvestre commented, we sholud have QE signoff first, then I think sylvestre’s request to go live.
15:15:15 <lizzard> i think there was a bug in the hotfix found this morning or last night. So QE will test again tonight and hopefully will be able to sign off.
15:15:23 <lizzard> But we aren’t quite there yet.
15:16:03 <jlund> lizzard: okay. I'm off in a few hours and it would be good to have more than one pair of releng eyes on the balrog rule that will be required for this.
15:16:14 <jlund> so it sounds like tomorrow is when we will need the rule?
15:16:19 <jlund> at the earliest?
15:18:08 <lizzard> likely softvision will test tonight and then sylvestre would be looking again in his morning…. so as early as then
ftr: I have not added a rule yet for this. this will need coordination of what the final hotfix that sticks will be and how it affects the OS_VERSION string. It would be good to get multiple eyes on this. Will check first thing in the morning on status
Comment 4•8 years ago
|
||
Adjusting the desired target based on the target audience of the hotfix
Summary: Adjust update target for Windows clients on 39-47 (inclusive) based on presence or absence of WebSense → Adjust update target for Windows clients on 40-47 (inclusive) based on presence or absence of WebSense
Updated•8 years ago
|
Assignee: nobody → bugspam.Callek
Summary: Adjust update target for Windows clients on 40-47 (inclusive) based on presence or absence of WebSense → Serve 48.0.2 updates to Windows users with "(nowebsense)" in update URL
Comment 5•8 years ago
|
||
Important note that Mac/Linux users won't have the "(nowebsense)" mark but should continue to receive updates.
Assignee | ||
Comment 6•8 years ago
|
||
Here is the details as I understand it:
# 1 - Update rules for release-cdntest [or maybe new release-websensetest?] so we can QA this before we ship it to users
# 2 once #1 is done, we can apply the same rules to "release" channel users.
For both sets:
* Users with (nowebsense) on *all* windows OS's get updated to 48.0.2 (unless they would have hit a prior watershed).
* Users without "(nowebsense)" on windows will get updated to 47 (unless they would have hit a prior watershed)
* Users on all other OS's will update as they would have prior to this hotfix shipping, thereby completely ignoring the hotfix in rules.
* We're not targetting any beta users with this hotfix/websense rule magic.
Is my understanding correct/valid?
Flags: needinfo?(sledru)
Flags: needinfo?(felipc)
Comment 7•8 years ago
|
||
LGTM, but bhearsum should confirm
Flags: needinfo?(felipc) → needinfo?(bhearsum)
Comment 8•8 years ago
|
||
comment 6 is as ben described it to me.
I'll repeat and rephrase to make sure we are on the same page.
* all windows users, we are whitelisting the windows users who have explicitly have the hotfix *and* their OS_VERSION includes the 'nowebsense' string. The other windows users: the ones who haven't got the hotfix yet or who do have the hotfix but also have websense, will continue to get the latest 47 release.
* all other platforms are unaffected
* Usual watersheds apply
Flags: needinfo?(bhearsum)
Comment 9•8 years ago
|
||
This looks like a great summary (I will reuse the content for the channel meeting :p)
Comment 10•8 years ago
|
||
And to detail more, once we have a websense fix/workaround/block in the product, we will be able to enable all updates.
Flags: needinfo?(sledru)
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Depends on: 1304765
Depends on: 1305787
You need to log in
before you can comment on or make changes to this bug.
Description
•