apt-get update && apt-get upgrade command failing in buildspec #102
Comments
|
Facing the same issue which is blocking account vending workflow |
|
Same issue. This is from mine [Container] 2022/04/19 20:27:26 Waiting for agent ping [Container] 2022/04/19 20:27:28 Running command pyenv global $PYTHON_38_VERSION [Container] 2022/04/19 20:27:28 Running command echo "Installing Ruby version 2.6 ..." [Container] 2022/04/19 20:27:28 Running command rbenv global $RUBY_26_VERSION [Container] 2022/04/19 20:27:30 Moving to directory /codebuild/output/src230558664/src [Container] 2022/04/19 20:27:30 Running command if [ -f manifest.yaml ];then export current=$(pwd);else if [ -f custom-control-tower-configuration/manifest.yaml ]; then export current=$(pwd)/custom-control-tower-configuration; else echo 'manifest.yaml does not exist at the root level of custom-control-tower-configuration.zip or inside custom-control-tower-configuration folder, please check the ZIP file'; exit 1; fi; fi; [Container] 2022/04/19 20:27:30 Running command apt-get update && apt-get upgrade -y Current default time zone: 'Etc/UTC' Setting up yarn (1.22.18-1) ... Configuration file '/usr/lib/jvm/java-1.8.0-amazon-corretto/jre/lib/security/policy/limited/local_policy.jar' [Container] 2022/04/19 20:29:48 Command did not exit successfully apt-get update && apt-get upgrade -y exit status 100 |
Workaround from @snebhu3 works |
|
@snebhu3 thanks for workaround! |
|
Workaround is good - thanks @snebhu3 |
|
We have released v2.3.0 which resolves this issue. |
Describe the bug
apt-get -q update 1> /dev/null && apt-get -q upgrade -y 1> /dev/nullcommand failing in buildspec with below error:Debug logs:
Impacted CFCT Version: Confirmed impact on version v2.2.0. Likely to impact older versions too.
Impacted CFCT Regions: Confirmed in us-west-2, likely to impact other regions too.
Workaround
Insert command :
apt-mark hold java-1.8.0-amazon-corretto-jdkin buildspec right before the impacted command:apt-get -q update 1> /dev/null && apt-get -q upgrade -y 1> /dev/nullThe text was updated successfully, but these errors were encountered: