You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A previous attempt (#2113) to update the Dockerfile and related scripts that are used to deploy the APT and YUM packages had to be reverted because we found that the deploy_agent workflow would fail even though local testing was successful.
The workflow fails right after starting the Docker container, with
>>> synchronizing local copy /data/s3/production with latest changes from ***
<botocore.awsrequest.AWSRequest object at 0x7f8c02e1eed0>
Exiting.
255
Error: Process completed with exit code 255.]
Some preliminary research suggests that there is an environment variable that can be set that will prevent that failure, but brief attempts to follow that guidance were met with failure. It may be that the environment variable wasn't set correctly or in the right location.
We need to re-apply the changes from #2113 and test the deploy_agent workflow (with options set so that only deploys APT and YUM, and deploys them to the "test" repo) and figure out how to resolve the failure.
The text was updated successfully, but these errors were encountered:
A previous attempt (#2113) to update the
Dockerfile
and related scripts that are used to deploy the APT and YUM packages had to be reverted because we found that thedeploy_agent
workflow would fail even though local testing was successful.The workflow fails right after starting the Docker container, with
Some preliminary research suggests that there is an environment variable that can be set that will prevent that failure, but brief attempts to follow that guidance were met with failure. It may be that the environment variable wasn't set correctly or in the right location.
We need to re-apply the changes from #2113 and test the
deploy_agent
workflow (with options set so that only deploys APT and YUM, and deploys them to the "test" repo) and figure out how to resolve the failure.The text was updated successfully, but these errors were encountered: