You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Frontend deploy workflow - Mix of old and new instances in production CMS load balancer during the deploy Push stage
Issue is observed at the push stage of the deploy workflow where the prod CMS load balancer has a mix of old instances and new instances with the new build.
Issue seems to be isolated to gyro projects where there is a separate ASG for the CMS load balancer.
To Reproduce
Production CMS ASG configs
`# -- CMS Launch Configuration/Autoscaling Group
Describe the bug
Frontend deploy workflow - Mix of old and new instances in production CMS load balancer during the deploy Push stage
Issue is observed at the push stage of the deploy workflow where the prod CMS load balancer has a mix of old instances and new instances with the new build.
Issue seems to be isolated to gyro projects where there is a separate ASG for the CMS load balancer.
To Reproduce
Production CMS ASG configs
`# -- CMS Launch Configuration/Autoscaling Group
@for container -in $containers
beam::container-config "$(environment)-cms-$(container)"
name: $container
file-backend: 'builds'
@beam::import-yaml: $container $environment cms
end
@EnD
aws::launch-configuration cms
name: "$project cms prod v$serial $brightspot-build"
ami: $ami-id
instance-type: "m5.xlarge"
key: $(aws::key-pair "base/key-pair")
instance-profile: $(aws::iam-instance-profile frontend)
security-groups: [$(aws::security-group frontend)]
enable-monitoring: true
end
aws::autoscaling-group cms
$(aws::subnet "base/private-$ (base-region)a"),
$(aws::subnet "base/private-$ (base-region)b")
name: $(aws::launch-configuration cms).name
launch-configuration: $(aws::launch-configuration cms)
subnets: [
]
health-check-type: "EC2"
classic-load-balancers: [
$(aws::load-balancer cms)
]
end`
Deployment workflow
`# -- Deployment Workflow
frontend-verify-hostname: "verify.($(aws::route53-hosted-zone base/public-zone).name)"
wildcard-frontend-verify-hostname: "*.verify.($(aws::route53-hosted-zone base/public-zone).name)"
cms-verify-hostname: "cms.verify.($(aws::route53-hosted-zone base/public-zone).name)"
@workflow::define aws::autoscaling-group frontend-deploy
@end`
Expected behavior
At the push stage only instances with the new build should be present in the production CMS load balancer
Stacktrace
If applicable, cut and paste any stacktrace or error message to help explain your problem.
Additional context
Opsdesk event https://beam-enterprise.opsdesk.cloud/p/l-opinion/events/00000193-01cd-d32a-a5ff-e5ef1feb0000
The text was updated successfully, but these errors were encountered: