shinesolutions/aem-platform-buildenv

Credential error when running Stack Builder integration tests using CodeBuild

Closed this issue · 1 comments

All AEM AWS Stack Builder builds currently fail due to credentials error below.
Initial investigation suggest this is a bug with boto(2) that is fixed in boto3, however, the sns_topic module that's currently used still uses boto(2).

TASK [ci-rhel7-aem62-consolidated - test-readiness-consolidated: Send message to SNS Topic] ***
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoAuthHandlerFound: No handler was ready to authenticate. 1 handlers were checked. ['HmacAuthV4Handler'] Check your credentials
fatal: [127.0.0.1]: FAILED! => changed=false
  msg: No handler was ready to authenticate. 1 handlers were checked. ['HmacAuthV4Handler'] Check your credentials
                to retry, use: --limit @/codebuild/output/src018859237/src/stage/aem-stack-manager-messenger-1.5.0/ansible/playbooks/send-message.retry

PLAY RECAP *********************************************************************
127.0.0.1                  : ok=8    changed=0    unreachable=0    failed=1

make[2]: *** [check-readiness-consolidated] Error 2
make[2]: Leaving directory `/codebuild/output/src018859237/src/stage/aem-stack-manager-messenger-1.5.0'
make[1]: *** [test-consolidated] Error 2
make[1]: Leaving directory `/codebuild/output/src018859237/src/stage/aem-stack-manager-messenger-1.5.0'
make: *** [test-integration-aem62-rhel7] Error 2

[Container] 2018/08/30 05:48:55 Command did not exit successfully make test-integration-$AEM_VERSION-$OS_TYPE test_id=$BUILD_ID exit status 2
[Container] 2018/08/30 05:48:55 Phase complete: BUILD Success: false
[Container] 2018/08/30 05:48:55 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: make test-integration-$AEM_VERSION-$OS_TYPE test_id=$BUILD_ID. Reason: exit status 2

A temporary solution has been put in place via shinesolutions/aem-stack-manager-messenger@e5de98f .
This temporary solution will no longer be needed when we eventually upgrade Ansible to the version that includes the updated sns module which uses boto3.