Broker version 1.0.2 will not run start on TAS 2.10 #216
Comments
|
It looks like you may have |
Good catch @coffee-squirrel - I'll get that taken care of. That should alleviate the second error. I think it's un-related though to the primary issue of I'll fix the (az)/(region) mapping and re-run. Thanks for the second set of eyes. |
|
I am seeing the similar error when installing with helm3, |
|
@jbogie-vmware please tell us if the service broker worked after you fixed the region name! |
|
@gid0 - Not really sure what's happening here. The update to the region in the tile config that was suggested by @coffee-squirrel was relevant to fixing the one error with the DNS lookup. I have successfully been able to install the broker on TAS 2.10 on AWS. I still intermittently receive the same error that @aad is receiving...only when I install the broker and TAS on GCP...and its intermittent...sometimes it installs fine...other times it does not. I'm going to treat that as an EDGE CASE as it's not a normal configuration for our customers. |
Describe the bug
The awslabs/aws-service broker v1.0.2 will not start on VMware Tanzu Application Service v2.10.2-build.90. During the final deployment of the
aws-sb-1.0.2into theaws-service-broker-spacethe application fails to start with the followingparamsbeing reported as not found:aws_access_keytarget_role_nameThere is an additional error stating that a request to
https://sts.ca-central-1a.amazonaws.com/failed to send. This error occurs no matter the region being used during deployment.Logs attached below, refer to lines 158-169.
To Reproduce
Install aws-service broker v1.0.2 and perform an initial deployment of the tile.
Expected behavior
aws-service broker v1.0.2 installs and deploys without error and services are able to be provisioned via the
cfcli.Environment (please complete the following information):
Additional context
Copy logs after the
+++indicator:+++
Using deployment 'aws-service-broker-6c1dd27ef316248bd6c9'
Task 214
Task 214 | 15:28:06 | Preparing deployment: Preparing deployment
Task 214 | 15:28:07 | Warning: Ambiguous request: the requested errand name 'deploy-all' matches both a job name and an errand instance group name. Executing errand on all relevant instances with job 'deploy-all'.
Task 214 | 15:28:08 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 214 | 15:28:08 | Preparing deployment: Preparing deployment (00:00:02)
Task 214 | 15:28:08 | Creating missing vms: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (00:01:08)
Task 214 | 15:29:16 | Updating instance deploy-all: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:18 | L executing pre-stop: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:18 | L executing drain: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:19 | L stopping jobs: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:20 | L executing post-stop: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:22 | L installing packages: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:24 | L configuring jobs: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:24 | L executing pre-start: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:25 | L starting jobs: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary)
Task 214 | 15:29:56 | L executing post-start: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (canary) (00:00:41)
Task 214 | 15:29:57 | Running errand: deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0) (00:00:40)
Errand 'deploy-all' completed with error (exit code 1)
Task 214 | 15:30:37 | Fetching logs for deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511 (0): Finding and packing log files (00:00:01)
Task 214 Started Thu Nov 26 15:28:06 UTC 2020
Task 214 Finished Thu Nov 26 15:30:38 UTC 2020
Exit code 1
Task 214 Duration 00:02:32
Task 214 done
Instance deploy-all/5a1cf2d6-1ad3-4865-a74e-0aef3b256511
Exit Code 1
Stdout cf version 6.51.0+2acd15650.2020-04-07
cf api https://api.sys.((REDACTED)).io --skip-ssl-validation
cf auth system_services ********
cf target -o aws-service-broker-org
cf create-space aws-service-broker-space
cf target -s aws-service-broker-space
cf push aws-sb-1.0.2 -n aws-sb -d apps.((REDACTED)).io -f /var/vcap/packages/aws_sb/manifest.yml -s cflinuxfs3 --no-start
cf set-env aws-sb-1.0.2 UAA_HOST https://uaa.sys.((REDACTED)).io
cf set-env aws-sb-1.0.2 CC_HOST https://api.sys.((REDACTED)).io
cf set-env aws-sb-1.0.2 LOGIN_HOST https://#.sys.((REDACTED)).io
cf set-env aws-sb-1.0.2 ROOT $HOME
cf set-env aws-sb-1.0.2 SCHEME https
cf set-env aws-sb-1.0.2 VERIFY_SSL true
cf set-env aws-sb-1.0.2 CF_ORG aws-service-broker-org
cf set-env aws-sb-1.0.2 CF_SPACE aws-service-broker-space
cf set-env aws-sb-1.0.2 CF_TARGET https://api.sys.((REDACTED)).io
cf set-env aws-sb-1.0.2 CF_SKIP_SSL true
cf set-env aws-sb-1.0.2 SECURITY_USER_NAME 0c5e7ea632fffd04
cf set-env aws-sb-1.0.2 SECURITY_USER_PASSWORD ********
cf set-env aws-sb-1.0.2 BROKER_ID gwnbroker
cf set-env aws-sb-1.0.2 AWS_ACCESS_KEY_ID ((REDACTED))
cf set-env aws-sb-1.0.2 AWS_SECRET_ACCESS_KEY ********
cf set-env aws-sb-1.0.2 AWS_DEFAULT_REGION ca-central-1a
cf set-env aws-sb-1.0.2 S3_BUCKET awsservicebroker
cf set-env aws-sb-1.0.2 S3_KEY templates/latest
cf set-env aws-sb-1.0.2 TEMPLATE_FILTER -main.yaml
cf set-env aws-sb-1.0.2 PRESCRIBE true
cf set-env aws-sb-1.0.2 S3_REGION us-east-1
cf set-env aws-sb-1.0.2 TABLE_NAME awssb
cf set-env aws-sb-1.0.2 VERBOSITY 5
cf start aws-sb-1.0.2
Starting app aws-sb-1.0.2 in org aws-service-broker-org / space aws-service-broker-space as system_services...
Stderr Using cflinuxfs3 stack
Start unsuccessful
1 errand(s)
===== 2020-11-26 15:31:17 UTC Finished "/usr/local/bin/bosh --no-color --non-interactive --tty --environment=10.0.16.10 --deployment=aws-service-broker-6c1dd27ef316248bd6c9 run-errand deploy-all"; Duration: 191s; Exit Status: 1
{"type":"step_finished","id":"errands.running.aws-service-broker-6c1dd27ef316248bd6c9.deploy-all","description":"Running errand deploy-all for AWS Service Broker"}
Exited with 1.2020/11/26 15:31:19 installation was unsuccessful
The text was updated successfully, but these errors were encountered: