GoCD rollback failed for edxapp

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Activity

Show:
Brian Beggs
May 30, 2017, 3:50 PM

I believe this is related to the fetch artifact refactor. The incorrect file is probably being fetched from upstream.

I have checked the ami_override.yml and it does not contain the current_asgs key (why would it, this is generated by the deploy stage!!)

it seems that the incorrect file is being passed to the script, the ami_deploy_info.yml script from the deploy stage should be used.

Looking deeper on this it seems that the ami_id that is in the ami_deploy_info.yml file would be used to deploy an AMI if the prior ASG was not available, but this does not seem correct. That ami_id is the newly deployed AMI not the AMI that was previously deployed.

Brian Beggs
May 30, 2017, 6:03 PM

https://github.com/edx/edx-gomatic/pull/339

This PR will allow the rollback to start pulling in the correct deploy file from the MD pipelines.

Brian Beggs
June 1, 2017, 2:07 PM

PR to fixup rollback via AMI_ID:
https://github.com/edx/tubular/pull/180

Fixed

Assignee

Brian Beggs

Reporter

Brian Beggs

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Sprint

None

Priority

CAT-1
Configure