MozillaWiki

ReleaseEngineering/How To/Shut off all updates: Difference between revisions

< ReleaseEngineering‎ | How To
(Created page with "{{Release Engineering How To|Shut off all updates}} On occasion we need to shut off all updates for all products/branches. This could happen because of a disastrous update sce...")
 
(→‎Shutting off updates: Update docs for how to find the global shut off rule)
 
(4 intermediate revisions by 2 users not shown)
Line 2: Line 2:
On occasion we need to shut off all updates for all products/branches. This could happen because of a disastrous update scenario, a downtime, or some other unforeseen reason.
On occasion we need to shut off all updates for all products/branches. This could happen because of a disastrous update scenario, a downtime, or some other unforeseen reason.


Currently our updates are split across two different systems (AUS3 and Balrog), so we need to make changes to both of those systems to do this:
= Shutting off updates =
= Shutting off updates in AUS3 =
* Go to [https://aus4-admin.mozilla.org/rules the Balrog Admin interface's rules page], VPN is required.
* Log on to aus3-staging via ssh (you should be able to log in with your own LDAP account)
* Find the rule with "Global shut off" in its "Comment" field (eg choose the "Firefox" Product/Channel filter and go to the last page)
* Run the following:
* Click the 'Update' button to modify the rule
sudo su -
* Change the priority to "10000" and click the "Save Changes" button
chmod 700 /opt/aus2/incoming
* Remove any filter to double check that shut off rule has highest priority (ie appears first in the list), so that it overrides all other rules


== Re-enabling ==
The load balancer will serve cached responses for a few minutes then all responses should be <tt><updates></updates></tt>.
Run the following:
chmod 755 /opt/aus2/incoming


= Shutting off updates in Balrog =
'''This affects all products, including Firefox, Thunderbird, GMP, SystemAddons, B2G, etc.'''
* Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
* Add a new rule with the following properties:
** Mapping: No-Update
** Background Rate: 100
** Priority: 100


== Re-enabling ==
== Re-enabling ==
* Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
* Go to [https://aus4-admin.mozilla.org/rules the Balrog Admin interface's rules page].
* Find the rule added in the previous section (be careful, as there are other No-Update rules that are in place for OS blocking. You want the one that doesn't specify _anything_ other than Mapping, Background Rate, and Priority).
* Find the rule with "Global shut off" in its "Comment" field. Change its priority to "1" and click the "Update" button.
* Change its "Priority" to 0 and click its "Update" button.

Latest revision as of 17:46, 2 August 2016

On occasion we need to shut off all updates for all products/branches. This could happen because of a disastrous update scenario, a downtime, or some other unforeseen reason.

Shutting off updates

  • Go to the Balrog Admin interface's rules page, VPN is required.
  • Find the rule with "Global shut off" in its "Comment" field (eg choose the "Firefox" Product/Channel filter and go to the last page)
  • Click the 'Update' button to modify the rule
  • Change the priority to "10000" and click the "Save Changes" button
  • Remove any filter to double check that shut off rule has highest priority (ie appears first in the list), so that it overrides all other rules

The load balancer will serve cached responses for a few minutes then all responses should be <updates></updates>.

This affects all products, including Firefox, Thunderbird, GMP, SystemAddons, B2G, etc.

Re-enabling

Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/How_To/Shut_off_all_updates&oldid=1142346"