cloudfoundry-community / kafka-service-broker-boshrelease

This BOSH release and deployment manifest deploy a cluster of kafka/kafka manager/zookeeper, plus a Cloud Foundry service broker
Apache License 2.0
9 stars 4 forks source link

Errand broker-registrar fails because it can't access system domain API endpoint (connect timeout) #15

Open odedia opened 5 years ago

odedia commented 5 years ago

Below is the output from the errand log. Should I setup something to enable access from the kafka-service-broker VM to the system domain API endpoint? I can access the system API endpoint from other deployments but from this particular one it appears to be blocked.

Thanks.

ubuntu@ops-manager-vm:~/kafka-service-broker-boshrelease$ bosh run-errand broker-registrar
Using environment '10.0.0.10' as client 'ops_manager'
Using deployment 'kafka-service-broker'
Task 386
Task 386 | 18:29:31 | Preparing deployment: Preparing deployment
Task 386 | 18:29:32 | Warning: Ambiguous request: the requested errand name 'broker-registrar' matches both a job name and an errand instance group name. Executing errand on all relevant instances with job 'broker
-registrar'.
Task 386 | 18:29:33 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 386 | 18:29:33 | Preparing deployment: Preparing deployment (00:00:02)
Task 386 | 18:29:33 | Creating missing vms: broker-registrar/afa3b5a8-6374-4144-945f-ecd2e5e9eb8b (0) (00:01:16)
Task 386 | 18:30:49 | Updating instance broker-registrar: broker-registrar/afa3b5a8-6374-4144-945f-ecd2e5e9eb8b (0) (00:00:13)
Task 386 | 18:31:02 | Running errand: broker-registrar/afa3b5a8-6374-4144-945f-ecd2e5e9eb8b (0) (00:00:15)
Task 386 | 18:31:17 | Fetching logs for broker-registrar/afa3b5a8-6374-4144-945f-ecd2e5e9eb8b (0): Finding and packing log files (00:00:01)
Task 386 Started  Sun May 26 18:29:31 UTC 2019
Task 386 Finished Sun May 26 18:31:18 UTC 2019
Task 386 Duration 00:01:47
Task 386 done
Instance   broker-registrar/afa3b5a8-6374-4144-945f-ecd2e5e9eb8b  
Exit Code  1  
Stdout     CF_API_URL=https://api.sys.pcf.pvtl.dev  
           CF_SKIP_SSL_VALIDATION=false  
           CF_ADMIN_USERNAME=admin  
           BROKER_NAME=starkandwayne-kafka  
           BROKER_URL=http://10.0.8.18:8080  
           BROKER_USERNAME=broker  
           Setting api endpoint to https://api.sys.pcf.pvtl.dev...  
           Request error: Get https://api.sys.pcf.pvtl.dev/v2/info: dial tcp 35.244.254.11:443: i/o timeout  
           TIP: If you are behind a firewall and require an HTTP proxy, verify the https_proxy environment variable is correctly set. Else, check your network connection.  
           FAILED  

Stderr     -  
1 errand(s)
Errand 'broker-registrar' completed with error (exit code 1)
Exit code 1
drnic commented 5 years ago

Yeah that’s strange. I wonder why your errand VM cannot reach the 35.x.y.z IP.