Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-82

dc-deployments-automation - historic AWS QS CFT Crowd hash fails to install Ansible dependencies due to issue with pipfile.lock

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • master
    • AWS Quick Start
    • None
    • Severity 3 - Minor

    Description

      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)

      Attachments

        Activity

          People

            Unassigned Unassigned
            bcostales Bernabe Theodore Costales III
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: