-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
provider/openstack stop before destroy #7184
provider/openstack stop before destroy #7184
Conversation
@alkersan Nice work! I agree -- creating an acceptance test that confirms end-to-end functionality for this is difficult. I think creating a simple test that verifies the new argument works without error is good enough. In this case, just make a copy of the "basic" acceptance test but add |
80548de
to
bddc422
Compare
@jtopjian ok, simple acc test is there and branch was rebased on fresh master |
bddc422
to
71924f9
Compare
@alkersan this looks great! I just ran the acceptance test suite and everything passed. Would you be able to squash the commits into two: one for the Gophercloud deps and the other for everything else? Once that's done, I'll go ahead and merge this in 😄 |
Docs and acceptance test included
71924f9
to
c32d152
Compare
@jtopjian done |
@alkersan Thank you, sir! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
@jtopjian Please review this patch for #7129 behavior. It includes 1 added dependency to
gophercloud
package and basic opt-in implementation of stop_before_destroy flag.Need advice on acceptance test for it. Currently it was tested manually within corporate openstack setup.
First scenario was a mini consul cluster, where clients were configured with
leave_on_terminate
option. When I scaled down consul machines - they correctly left cluster and disappeared from node catatlog, thus it subjectively proves that Nova sent ACPI shutdown signal to guests OS. Withoutstop_before_destroy
consul shows all nodes in failing state.Another check is to peek at instance action history API. With
stop_before_destroy
enabled, action history should includestop
:But, unfortunately, I didn't find implementation of history API in
gophercloud