ReleaseEngineering/How To/Shut off all updates

< ReleaseEngineering‎ | How To
Revision as of 14:26, 13 November 2013 by Bhearsum (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 in AUS3

  • Log on to aus3-staging via ssh (you should be able to log in with your own LDAP account)
  • Run the following:
sudo su -
chmod 700 /opt/aus2/incoming

Re-enabling

Run the following:

chmod 755 /opt/aus2/incoming

Shutting off updates in Balrog

Re-enabling

  • Go to 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).
  • Change its "Priority" to 0 and click its "Update" button.