Transient error with "Create new revision" step, import boto

Last night we were unable to do new deployments through CircleCI. We had no problems earlier and it seems to have resolved itself this morning. It was failing on a “Create new revision” step, with this stack trace:

create_application_revision /tmp/codedeploy_applications.json /tmp/codedeploy_revisions.json
Traceback (most recent call last):
  File "/usr/local/bin/create_application_revision", line 9, in <module>
    load_entry_point('circle-sds-support==0.8.2', 'console_scripts', 'create_application_revision')()
  File "build/bdist.linux-x86_64/egg/", line 351, in load_entry_point
    """Does the package's distribution contain the named metadata?"""
  File "build/bdist.linux-x86_64/egg/", line 2363, in load_entry_point
  File "build/bdist.linux-x86_64/egg/", line 2088, in load
    return urlunparse(parsed[:-1] + ('',))
  File "/usr/local/lib/python2.7/dist-packages/circlesds/", line 13, in <module>
    import as sds
  File "/usr/local/lib/python2.7/dist-packages/circlesds/aws/", line 11, in <module>
    import as s3
  File "/usr/local/lib/python2.7/dist-packages/circlesds/aws/", line 3, in <module>
    import boto
  File "/usr/local/lib/python2.7/dist-packages/boto/", line 28, in <module>
    from boto.storage_uri import BucketStorageUri, FileStorageUri
  File "/usr/local/lib/python2.7/dist-packages/boto/", line 27, in <module>
    from boto.s3.deletemarker import DeleteMarker
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/", line 26, in <module>
    from boto.regioninfo import RegionInfo, get_regions
  File "/usr/local/lib/python2.7/dist-packages/boto/", line 28, in <module>
    from boto.endpoints import BotoEndpointResolver
  File "/usr/local/lib/python2.7/dist-packages/boto/", line 13, in <module>
    import boto.vendored.regions.regions as _regions
ImportError: No module named regions.regions

((create_application_revision "/tmp/codedeploy_applications.json" "/tmp/codedeploy_revisions.json")) returned exit code 1

Action failed: Create new revision of apiserver

Any idea what could have caused this?