https://sentry.prod.mozaws.net/operations/socorro-new-stage/issues/684197/ TypeError: argument of type 'NoneType' is not iterable File "crontabber/app.py", line 1053, in _run_one for last_success in self._run_job(job_class, config, info): File "crontabber/base.py", line 189, in main function() File "crontabber/base.py", line 259, in _run_proxy return self.run(*args, **kwargs) File "socorro/cron/jobs/upload_crash_report_json_schema.py", line 50, in run connection = connection_context._connect() File "socorro/external/boto/connection_context.py", line 201, in _connect **self._get_credentials() File "boto/__init__.py", line 140, in connect_s3 return S3Connection(aws_access_key_id, aws_secret_access_key, **kwargs) File "boto/s3/connection.py", line 190, in __init__ validate_certs=validate_certs, profile_name=profile_name) File "boto/connection.py", line 572, in __init__ host, config, self.provider, self._required_auth_capability()) File "boto/auth.py", line 930, in _wrapper if '.cn-' in self.host: I think there are a couple of possibilities: 1. the crontabber container is missing some configuration or some configuration in the docker/config/ files is wrong 2. the TelemetryS3CrashStorage needs some code fixes to work with the auth scheme we're using in -stage-new This bug covers fixing this.
As an aside, I didn't realize crontabber used the TelemetryS3 bucket. I'm not sure any of that works right in the local development environment. Should look into that as well.
Making this a P1. This blocks the new infrastructure work.
Bug #1410167 fixes some TelemetryS3CrashStorage configuration. After that lands, I'll work on this.