Skip to content
This repository has been archived by the owner on Jul 10, 2021. It is now read-only.

CloudFormation stack template does not work #1546

Open
mutabletao opened this issue Oct 20, 2019 · 13 comments
Open

CloudFormation stack template does not work #1546

mutabletao opened this issue Oct 20, 2019 · 13 comments

Comments

@mutabletao
Copy link

Page: /setup/install/providers/aws/aws-ec2/

Feedback: running the provided stack template with recommended parameters fails with the message : Unresolved resource dependencies [SpinnakerInstanceProfile] in the Outputs block of the template

@dorbin
Copy link
Contributor

dorbin commented Oct 21, 2019

@spinnakerbot
Copy link
Contributor

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

@clareliguori
Copy link
Member

cc @saimadineni

@spinnakerbot
Copy link
Contributor

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

@aleon1220
Copy link
Contributor

what i dont like is that these issues never get ressolved. Is there any status on this? I had similar error and the problem was the IAM configuration plus cloud driver was not enabled....

@the-mikedavis
Copy link

@spinnakerbot remove-label to-be-closed

seeing this with the AWS console & the CLI

$ aws cloudformation deploy --stack-name spinnaker-managing-infrastructure-setup --template-file managing.yaml --parameter-overrides UseAccessKeyForAuthentication=true --capabilities CAPABILITY_NAMED_IAM --region us-east-2
An error occurred (ValidationError) when calling the CreateChangeSet operation: Unresolved resource dependencies [SpinnakerInstanceProfile] in the Outputs block of the template 

Screen Shot 2020-03-10 at 11 45 30 AM

Is there a change that we can make to the managing.yaml as a workaround?

@roybaryosef-spotinst
Copy link

Getting the same issue, couldn't find the proper documentation to work around this.

@317brian
Copy link
Contributor

@akshayabd any update on this?

@akshayabd
Copy link
Contributor

I've added it in the agenda to discuss in next week's AWS SIG meeting:
https://docs.google.com/document/d/1TB7dSQDTM9jFBsttuevxOsP6MGQ3-z0wrYMIGxYxhYQ/edit#

@akshayabd
Copy link
Contributor

We discussed this in the SIG meeting today. These docs are too outdated and just updating the EKS version isn't correct.

@pauljrob is working on a new version of the docs. In the meantime he recommends users follow https://aws.amazon.com/blogs/opensource/continuous-delivery-spinnaker-amazon-eks/

So the recommendation is to remove the existing docs and just point to the article above. Once a new version of the docs is available @pauljrob will create a PR for it.

@317brian
Copy link
Contributor

We should add a blurb to the page that will point users to that aws page while the spinnaker.io page is being worked on.

@akshayabd
Copy link
Contributor

We should add a blurb to the page that will point users to that aws page while the spinnaker.io page is being worked on.

Apologies I haven't gotten to this yet - WIP

@akshayabd
Copy link
Contributor

#1763 opened for review

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants