1216381 - Android repacks try to run balrog-release-pusher.py on aus4-admin-dev, fails when ruleID's don't match

Status: RESOLVED WORKSFORME

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

Description

[Nick Thomas [:nthomas] (UTC+12)]

Spun out from bug 1201383. We waste some time retrying balrog-release-pusher.py against staging Balrog, but fail because we're trying to use production ruld ids.

eg http://archive.mozilla.org/pub/mozilla.org/mobile/candidates/42.0b6-candidates/build1/logs/release-mozilla-beta-android-api-9_repack_1-bm94-build1-build8.txt.gz

[call to release pusher succeeds against production, then ...]
16:50:05     INFO - Calling Balrog release pusher script
16:50:05     INFO - retry: Calling run_command with args: (['python', '/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/balrog-release-pusher.py', '--build-properties', '/builds/slave/rel-m-beta-and-api-9_rpk_1-000/balrog_props.json', '--buildbot-configs', 'https://hg.mozilla.org/build/buildbot-configs', '--release-config', '/builds/slave/rel-m-beta-and-api-9_rpk_1-000/build/buildbot-configs/mozilla/release-fennec-mozilla-beta.py', '--credentials-file', '/builds/slave/rel-m-beta-and-api-9_rpk_1-000/oauth.txt', '--release-channel', 'beta', '--api-root', 'https://aus4-admin-dev.allizom.org/api', '--username', 'stage-ffxbld'],), kwargs: {'cwd': '/builds/slave/rel-m-beta-and-api-9_rpk_1-000/build'}, attempt #1
...
16:50:10     INFO -  Starting new HTTPS connection (1): aus4-admin-dev.allizom.org
16:50:10     INFO -  /builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/vendor/requests-2.7.0/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
16:50:10     INFO -    InsecurePlatformWarning
16:50:12     INFO -  Starting new HTTPS connection (1): aus4-admin-dev.allizom.org
16:50:12     INFO -  /builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/vendor/requests-2.7.0/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
16:50:12     INFO -    InsecurePlatformWarning
16:50:13     INFO -  Caught HTTPError:
16:50:13     INFO -  Starting new HTTPS connection (2): aus4-admin-dev.allizom.org
16:50:13     INFO -  /builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/vendor/requests-2.7.0/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
16:50:13     INFO -    InsecurePlatformWarning
16:50:13     INFO -  Caught HTTPError:
16:50:13     INFO -  Traceback (most recent call last):
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/balrog-release-pusher.py", line 121, in <module>
16:50:13     INFO -      release_config['buildNumber'], testChannelRuleIds)
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/balrog/submitter/cli.py", line 467, in run
16:50:13     INFO -      ).update_rule(mapping=name)
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/balrog/submitter/api.py", line 219, in update_rule
16:50:13     INFO -      return self.request(method='POST', data=rule_data)
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/balrog/submitter/api.py", line 102, in request
16:50:13     INFO -      return self.do_request(url, data, method)
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/balrog/submitter/api.py", line 119, in do_request
16:50:13     INFO -      req.raise_for_status()
16:50:13     INFO -    File "/builds/slave/rel-m-beta-and-api-9_rpk_1-000/tools/scripts/updates/../../lib/python/vendor/requests-2.7.0/requests/models.py", line 851, in raise_for_status
16:50:13     INFO -      raise HTTPError(http_error_msg, response=self)
16:50:13     INFO -  requests.exceptions.HTTPError: 404 Client Error: NOT FOUND
16:50:13    ERROR - Return code: 1
16:50:13     INFO - retry: Failed, sleeping 60 seconds before retrying

The dual submission comes from https://dxr.mozilla.org/mozilla-central/rev/1a157155a4fe0074b3d03b54fe9e466472c2cd56/testing/mozharness/configs/balrog/production.py and https://dxr.mozilla.org/build-central/source/mozharness/mozharness/mozilla/updates/balrog.py#95

Kinda makes sense to submit into blobs in staging for nightlies and releases, but the pushing isn't going to work and isn't really valuable.

Comment 1

[Julien Cristau [:jcristau]]

We have different configs for prod vs staging nowadays, and aren't publishing android builds in balrog.