-
Notifications
You must be signed in to change notification settings - Fork 190
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
Nodes are not powered down on make clean and cause side effects #906
Comments
Is this problem still occurring? |
I think so yes, this was a problem when masters were not totally bootstrapped and vm was still there. But the issue as it was, is that i was expecting nodes to be powered down on make clean, and this is not happening. |
This is expected as we've not got any destroy support for IPI baremetal in the installer yet ref openshift/installer#2005 We could hack around it in a dev-scripts specific way (ipmitool etc), but I'm not sure it's worth it since we expect the end-user interface to be the installer. |
When I run |
We're tracking this as a wish list item to implement proper cluster destroy in the installer /close |
@stbenjam: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When i execute a
make clean
command, I expected that my nodes (masters/workers) are powered down. But that is not the case, while the bootstrap VM is powered down, losing all the services that were used by masters, such as coredns.As a side effect, masters are still querying for addresses like api-int (resolved in the past by bootstrap vm), and this is causing a saturation (max queries reached) on the dns service of the installer host.
The text was updated successfully, but these errors were encountered: