cloudfoundry-attic / bosh-init

bosh-init is a tool used to create and update the Director VM
Apache License 2.0
31 stars 33 forks source link

bosh vms --dns return two dns name for a vm #108

Closed chrisrana closed 7 years ago

chrisrana commented 7 years ago

I am using bosh-init,bosh-257.9.tgz and cf-233 .Stemcell 3262.2

DNS host name is not resolving while deploying cloud foundry.On exploring I get two entry for cloud controller and other vm in powerdns db postgres.

95a07d80-3fb8-40db-8a13-3c295755b066.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh 0.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh

In horizone

95a07d80-3fb8-40db-8a13-3c295755b066 is not VM instance ID ,but it is present in metdata section of of the VM NAME cloud_controller/95a07d80-3fb8-40db-8a13-3c295755b066 DEPLOYMENT cf-installer-team-test ID 95a07d80-3fb8-40db-8a13-3c295755b066

image

These two host name is not pingable in director and in respective VM as well. 0.consul.ccc-bosh-net.cf-installer-team-test.microbosh 0.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh

bosh vms --dns

| cloud_controller/0 | starting | large | 10.20.0.231 | 95a07d80-3fb8-40db-8a13-3c295755b066.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh | | | | | | 0.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh |

| consul/0 | running | small | 10.20.0.232 | 48d2b0a4-8533-4b7d-a3c5-b11ab463e910.consul.ccc-bosh-net.cf-installer-team-test.microbosh | | | | | | 0.consul.ccc-bosh-net.cf-installer-team-test.microbosh

powerdns entry in postgres DB.

4 | 0.consul.ccc-bosh-net.cf-installer-team-test.microbosh | A | 10.20.0.232

5 | 0.20.10.in-addr.arpa | SOA | localhost hostmaster@localhost 0 10800 604800 30

6 | 0.20.10.in-addr.arpa | NS | ns.microbosh

7 | 232.0.20.10.in-addr.arpa | PTR | 0.consul.ccc-bosh-net.cf-installer-team-test.microbosh

8 | 48d2b0a4-8533-4b7d-a3c5-b11ab463e910.consul.ccc-bosh-net.cf-installer-team-test.microbosh | A | 10.20.0.232

9 | 232.0.20.10.in-addr.arpa | PTR | 48d2b0a4-8533-4b7d-a3c5-b11ab463e910.consul.ccc-bosh-net.cf-installer-team-test.mi crobosh

**10 | 0.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh | A | 10.20.0.231

11 | 231.0.20.10.in-addr.arpa | PTR | 0.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh

12 | 95a07d80-3fb8-40db-8a13-3c295755b066.cloud-controller.ccc-bosh-net.cf-installer-team-test.microbosh | A | 10.20.0.231

13 | 231.0.20.10.in-addr.arpa | PTR | 95a07d80-3fb8-40db-8a13-3c295755b066.cloud-controller.ccc-bosh-net.cf-installer-te** am-test.microbosh 1 | microbosh | SOA | localhost hostmaster@localhost 0 10800 604800 30 2 | microbosh | NS | ns.microbosh 3 | ns.microbosh | A |


bosh-init.yml

`<% load 'bosh-init/bosh-init.rb' %>

name: <%= $os_tenant %>

releases:

resource_pools:

disk_pools:

networks:

jobs:

cloud_provider: template: {name: openstack_cpi, release: bosh-openstack-cpi}

ssh_tunnel: host: <%=$bosh_director_ip %> # <--- Replace with a floating IP port: 22 user: vcap private_key: <%= $key_file %> # Path relative to this manifest file

mbus: "https://mbus:mbus-password@<%=$bosh_director_ip %>:6868" # <--- Replace with a floating IP

properties: openstack: openstack agent: {mbus: "https://mbus:mbus-password@0.0.0.0:6868"} blobstore: {provider: local, path: /var/vcap/micro_bosh/data/cache} ntp: ntp `

dpb587-pivotal commented 7 years ago

Closing in favor of https://github.com/cloudfoundry/bosh/issues/1439 - bosh-init is used to start the director running, so this seems like a bosh or configuration issue instead.