Cloudformation fails & rollsback - GitLab failing to build?

Six Stars

Cloudformation fails & rollsback - GitLab failing to build?

I've tried to build the datalake about 6 times (us-east-1, us-east-2). It keeps failing and rolling back. This time, I was watching and saw that it failed trying to create GitLab. I'm not sure if that's the only issue. Can someone verify that this version of the cloudformation script works for them or if it's broken?

 

Thank you!

Employee

Re: Cloudformation fails & rollsback - GitLab failing to build?

Can you provide a screenshot of the values you are providing on the Quickstart Form? Post it as an attachment here.  I'll review it.

 

Also, after you have filled in the Quickstart form and click Next, the following page has a "Rollback on Failure" radio button option under the "Advanced" settings.  Please select "No".  This will keep your stacks open even if they fail.

 

So assuming the problem is with the Gitlab server you can ssh onto that server with the key you used for the cloud formation.  The user is ubuntu.  Once you are logged in, please take a look at the /var/log/cfn-init.log file.  It may be pretty long, so go to the end and take a look.  That is usually where any errors occur.  If you can post that here as well it would be helpful.

Employee

Re: Cloudformation fails & rollsback - GitLab failing to build?

I can confirm that I just rant the usual install in us-east-2 with a license in us-east-2 and ran fine.  I selected the option for the stack to create a GitLab instance for me by leaving the field blank.  See attached screenshot of AWS Quickstart form.  Without a log or error message it is difficult to further diagnose your problem.  Please send your screenshots and log via a private message by clicking on my userid and selecting Send Message..

Six Stars

Re: Cloudformation fails & rollsback - GitLab failing to build?

I tried another attempt at launching the stack and I was able to get it to work. What I did differently this time is, I used simpler passwords. After getting an error that Redshift couldn't use the password I gave. So perhaps it wasn't picking that I was using some special characters that might not be allowed? 

 

This format of a password worked

rnXDcJemb9nw!

 

This might not have

sNOBgZsW6.j~

 

Thank you for the help!