spinnaker: “Create Load Balancers” Pipeline step config. throwing error (AWS)

Issue Summary:

“Create Load Balancers” Pipeline step doesn’t seem to be set up for AWS

Cloud Provider(s):

AWS

Environment:

Spinnaker 1.7.4, Ubuntu 16.04 LTS, installed via Halyard (1.2.0), running in AWS.

Feature Area:

Pipelines

Description:

Hi! After enabling the infrastructure stages (in a pretty unusual way, see Steps to Reproduce below), I can add the “Create Load Balancers” step to a Pipeline just fine, but clicking “(+) Add load balancer” gives me a JavaScript error in the Console:

angular.js:14525 Error: One of component or template or templateUrl options is required.
    at Object.$modal.open (ui-bootstrap-tpls.js:4476)
    at Object.$delegate.open (uibModalRejections.ts:11)
    at createLoadBalancerStage.js:40
    at processQueue (angular.js:16832)
    at angular.js:16876
    at Scope.$digest (angular.js:17971)
    at angular.js:18200
    at completeOutstandingRequest (angular.js:6274)
    at angular.js:6554 "Possibly unhandled rejection: {}"

Upon looking at Deck’s ‘compiled’ JavaScript code (/opt/deck/html/app.js), I see calls for many cloudProviderRegistryProvider.registerProvider('<provider_name>’, { <provider_settings> }) Most have the loadBalancer.createLoadBalancerTemplateUrl setting (DC/OS, Azure, Cloud Foundry, Kubernetes, OpenStack, GCE, App Engine), but not AWS?

What I’m concluding is that this isn’t actually “set up” for AWS in Deck?

In the end, I’m wondering if the “Create Load Balancer” Pipeline step for AWS is even supposed to work, or it’s just not been added (yet), and if not if there’s a reason.

Note that I can create Load Balancers fine in the UI otherwise. I have already baked AMIs and deployed clusters. It all works great.

Thanks a lot!

Steps to Reproduce:

1. Enable the infrastructure stages feature:
   1. hal config features edit --infrastructure-stages true
   2. Note: This doesn’t actually do anything for me (AWS), which warrants me to do the next steps
2. Create a settings-local.js in hal config:
   1. echo "window.spinnakerSettings.feature.infrastructureStages = true;" > ~/.hal/default/profiles/settings-local.js
3. Apply:
   1. sudo hal deploy apply
4. Fix the permission of deployed setttings-local.js
   1. sudo chmod 644 /opt/deck/html/settings-local.js
   2. Note: That file gets a 600 permission, owned by “spinnaker:spinnaker” so Apache (“www-data”) can’t read it as-is, the browser throwing a 403. Not sure if this is expected behaviour or if “hal” should even be run as root altogether.
5. Create Pipeline > Add stage > Type: Create Load Balancer > (+) Add load balancer

Additional Details:

I figured that doing hal config features edit --infrastructure-stages true should have enabled it if it were available (I don’t have any other providers to test), and that this override in settings-local.js is somewhat forcing it and I probably shouldn’t even see that Pipeline step appear.