Ubuntu
juju-core package

  1. Bug #1364037
  2. Comment #4

Comment 4 for bug 1364037

Revision history for this message
santhosh (santhoshb2610) wrote :

Hi this is santhosh,

ran into same kind of issue. when i specify a particular vpc-id ( it is not default so i did vpc-id-force). it bootstraps controller in that vpc and was loosing/cannot connect to the api after that. BELOW IS THE BOOTSTRAP COMMAND I GAVE:

ubuntu@x86inst-1a:~$ juju bootstrap --config "vpc-id=vpc-08b1e3735cf3" --config "vpc-id-force=true" aws test

it gives the error as below:

ERROR unable to contact api server after 1 attempts: unable to connect to API: dial tcp 172.86.1.14:17070: connect: connection refused

*IF IT CAN REACH THE VPC AND CAN BOOTSTRAP CONTROLLER IN PARTICULAR VPC, WHY IS IT UNABLE TO REACH OR RUNNING INTO API ERROR(17070) AFTER BOOTSTRAP.
*WHY DID JUJU EXPECT IT TO BE PUBLIC, IF I GIVE VPC AS PARAMETER WHY CAN'T IT ACCEPT WHAT SHOULD I DO TO MAKE IT ACCEPT BUT NEED IT TO BE PRIVATE AS FOR THE SECURITY CONCERNS.