search

Qarik-Group / bucc-walk-thru-aws

This is an example repository that compliaments a walk-thru video of provisioning AWS networking, a public Jumpbox, a private BOSH/UAA/CredHub/Concourse (BUCC), and an example 5-node ZooKeeper cluster.
https://github.com/starkandwayne/bucc
7 stars 4 forks source link

using wrong certificate when createing bosh/0 instance #1

Open httran13 opened 5 years ago

httran13 commented 5 years ago

Hello, I am getting an error inside the jumpbox after running bucc up and trying to create a bosh/0 instance.

It seems like a Post to the bosh instance is using a certificate made for the virtualbox deployment(192.168.50.6)

can help me where in the configs is it using that certificate. Thanks


  Creating VM for instance 'bosh/0' from stemcell 'ami-1974417c light'... Finished (00:01:42)
  Waiting for the agent on VM 'i-087756894670939e3' to be ready... Failed (00:00:33)
Failed deploying (00:02:15)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
  Creating instance 'bosh/0':
    Waiting until instance is ready:
      Post https://mbus:<redacted>@10.10.1.4:6868/agent: x509: certificate is valid for 192.168.50.6, not 10.10.1.4

Exit code 1```
drnic commented 5 years ago

@rkoster @ramonskie any thoughts?

httran13 commented 5 years ago

Hi guys after some trail and error, some light may be shed, when running envs/bucc/bin/update-upon-jumpbox

the bucc up commands uses the --lite flags and vbox cpi. Looks like somewhere between when my local copy and the jumpbox copy envs may not had completely transported to jumpbox Hope that helps. I'll continue to learn more about the inner workings, i've only tried to follow along in the readme

drnic commented 5 years ago

@httran13 I appreciate that you're continuing to debug this. I'm not sure when I'll be able to create time to go thru the walk thru and debug it; so I'm sorry that you're getting this opportunity :)

But, the project is called "bucc-walk-thru-aws" and you mentioned the "vbox" CPI. Perhaps go thru the walk thru on AWS to see it to the end, and then make adjustments for virtualbox on next walk thru?

drnic commented 5 years ago

Note, when switching CPIs use bucc clean to remove the state folder and cached config files.

httran13 commented 5 years ago

@httran13 I appreciate that you're continuing to debug this. I'm not sure when I'll be able to create time to go thru the walk thru and debug it; so I'm sorry that you're getting this opportunity :)

But, the project is called "bucc-walk-thru-aws" and you mentioned the "vbox" CPI. Perhaps go thru the walk thru on AWS to see it to the end, and then make adjustments for virtualbox on next walk thru?

Thanks doc! i actually got bucc running after cleaning out my entire env and instead ran bucc up locally instead of through jumpbox. I'll run through it again using jumpbox and see why its executing virtualbox and --lite there.

In the mean time, running bucc info gives me the private ip of concourse that is inaccessible, there's no mention of anyway to access it and bucc fly doesn't set any configurations. LMK if this was intended or how i can modify it so that bucc info url returns some pipe through the jumpbox

ramonskie commented 5 years ago

@httran13 bucc on virtualbox +jumpbox is probably not going to work unless you setup the correct network configuration on your host and virtualbox network.

i would suggest to only use the walktrough on aws,google,azure. also take a look at our blog posts about bucc https://starkandwayne.com/blog/tag/bucc/

that said. run a clean bucc by cloning https://starkandwayne.com/blog/tag/bucc/ in a new terminal and just run bucc up this will setup bucc in virtualbox and you would be able to contact concourse with bucc info

httran13 commented 5 years ago

@httran13 bucc on virtualbox +jumpbox is probably not going to work unless you setup the correct network configuration on your host and virtualbox network.

i would suggest to only use the walktrough on aws,google,azure. also take a look at our blog posts about bucc https://starkandwayne.com/blog/tag/bucc/

that said. run a clean bucc by cloning https://starkandwayne.com/blog/tag/bucc/ in a new terminal and just run bucc up this will setup bucc in virtualbox and you would be able to contact concourse with bucc info

Sorry there's some confusion with what i stated before, I didn't wanted to run vbox, when following the readme and executing

envs/bucc/bin/update-upon-jumpbox

from my understanding, update-upon-jumpbox script is suppose to upload my current configuration and execute bucc up from the jumpbox using aws cpi, but instead it used the vbox cpi with --lite flag, hence i suspect is how this error is occurring:

      Post https://mbus:<redacted>@10.10.1.4:6868/agent: x509: certificate is valid for 192.168.50.6, not 10.10.1.4

I have went through the bucc vbox deployment, which is why i noticed 192.168.50.6

Also when the update-upon-jumpbox executed, it output the cpi and --lite flag which wasn't expected.

httran13 commented 5 years ago

Hello im able to get bucc up and access concourse by using a LB, but when interacting with dashboard, it routes me using the private ip as shown bottom left

image