spinnaker: CloudFormation deploy stage waits indefinitely even after successful deploy
Issue Summary:
CloudFormation deploy stage waits for completion indefinitely even after successful deployment.
Cloud Provider(s):
AWS
Environment:
Halyard deployed on an EC2 instance. Version 1.13.2.
Feature Area:
AWS, CloudFormation Deploy, CloudDriver
Steps to Reproduce:
Using an AWS Lambda CloudFormation stack, deploying a lambda from zip in S3 bucket.
Stage json:
{
"credentials": "aws-saas",
"name": "Deploy (CloudFormation Stack)",
"parameters": {},
"regions": [
"eu-west-2"
],
"source": "text",
"stackName": "LambdaTestStack",
"templateBody": {
"AWSTemplateFormatVersion": "2010-09-09",
"Description": "A template for creating a simple lambda function.",
"Outputs": {},
"Parameters": {},
"Resources": {
"ToUpperLambdaFunction": {
"Properties": {
"Code": {
"S3Bucket": "test-lambda-packages",
"S3Key": "LambdaTestPackage.zip"
},
"Handler": "LambdaTest::LambdaTest.Function::FunctionHandler",
"Role": "arn:aws:iam::XXXXXXXXXXXX:role/service-role/LambdaTest-role-96nueea8",
"Runtime": "dotnetcore2.1"
},
"Type": "AWS::Lambda::Function"
}
}
},
"type": "deployCloudFormation"
}
The following appears repeatedly in the logs: c.n.s.orca.clouddriver.OortService : [anonymous] <— HTTP 404 http://localhost:7002/aws/cloudFormation/stacks/arn:aws:cloudformation:eu-west-2:XXXXXXXXXXXX:stack/LambdaTestStack/19d2dd30-5c41-11e9-a064-0234cd8b818c
@xavileon many thanks.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 32
That did it for me, many thanks!
Works now, also had to do this:
In .hal/default/profiles/clouddriver-local.yml - add
But - how can we instruct people to do the same? Should this be a Halyard-thingy which sets this in Clouddriver? I’d expect more issues like this if this is not “asked” - but the “CloudFormation” stage stays in the UI…