Creating a Load Balancer with a Subnet fails with, Default VPC not found, when not using default

#1

When we set the Subnet during the configuration of the Deployment Cluster. However, once we save the changes the VPC Subnet is empty from the stage view. The pipeline there after fails with VPC [none] (The functionality you requested is not available in this region). Attempting to create a Load Balancer with the Subnet we’ve registered with the tag fails with “Default VPC not found”. Querying the Spinnaker Api (http://localhost:8084/subnets/aws) returns the Subnets with the “state”:“available” and no null values. Otherwise, creating a firewall for our VPC succeeds.