Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap DNS entry hangs around (libvirt) #878

Closed
rphillips opened this issue Dec 11, 2018 · 0 comments
Closed

Bootstrap DNS entry hangs around (libvirt) #878

rphillips opened this issue Dec 11, 2018 · 0 comments

Comments

@rphillips
Copy link
Contributor

Version

$ openshift-install version
bin/openshift-install v0.5.0-master-75-gfb40d022b42d233ea1f199791cf553344552c585
Terraform v0.11.10
$ ~/.terraform.d/plugins/terraform-provider-libvirt -version  # only needed if you're using libvirt
Compiled against library: libvirt 4.8.0
Using library: libvirt 4.8.0
Running hypervisor: QEMU 3.0.0
Running against daemon: 4.8.0

Platform (aws|libvirt|openstack):

libvirt

What happened?

On a successful deployment, the bootstrap machine gets destroyed and terminated successfully; however, the DNS entry for the booststrap machine hangs around:

test1-api.tt.testing.   0       IN      A       192.168.126.10
test1-api.tt.testing.   0       IN      A       192.168.126.11

What you expected to happen?

The 192.168.126.10 A record should be removed. The kubectl command exhibits a small timeout trying to communicate with 192.168.126.10, but otherwise completes successfully when it tries the .11 address.

How to reproduce it (as minimally and precisely as possible)?

$ openshift-install create cluster --log-level=debug --dir=test1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant