Issue Summary

We found that from a customer report, there was an issue with Ansible SSM pin hash of fc39d2bb23b45121c5281ef6d8eed2987ba233d9 fails to deploy Crowd properly due to issues with Pipfile.lock failing to initialize properly. After switching the Ansible hash to a different build, this started working properly. This ticket serves as notice regarding the broken hash.

Steps to Reproduce

• Using CloudFormation, use the hash fc39d2bb23b45121c5281ef6d8eed2987ba233d9 to deploy a Crowd installation

Expected Results

• Crowd is successfully deployed

Actual Results

• Crowd fails to deploy due to pipfile.lock issue

Workaround

• Use a different SHA-1 hash for the pin (latest or another known good version)