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
OpenStack: Deleting servers using tag-based filtering #3818
OpenStack: Deleting servers using tag-based filtering #3818
Conversation
To save others the trouble to look it up, this was introduced in gophercloud v0.7.0, and we're using v0.8.0. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Now to delete servers we first get a list of all available servers from Nova, and then we iterate through them to find those with required metadata. In the case of a large number of servers, this can take a very long time. Fortunately gophercloud introduced filtering by tags, so we can start using this feature to get only servers with the required tag. gophercloud/gophercloud#1759
/recheck |
/retest |
/test e2e-openstack |
/lgtm |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
10 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
In openshift#3818 we introduced tag-based server delition. Unfortunately it turned out we can destroy servers, created by previous versions, as no tags were set there. To fix this situation we come back to the previous solution - deleting servers by metadata.
In openshift#3818 we introduced tag-based server delition. Unfortunately it turned out we can destroy servers, created by previous versions, as no tags were set there. To fix this situation we come back to the previous solution - deleting servers by metadata.
In openshift#3818 we introduced tag-based server delition. Unfortunately it turned out we can destroy servers, created by previous versions, as no tags were set there. To fix this situation we come back to the previous solution - deleting servers by metadata.
In openshift#3818 we introduced tag-based server delition. Unfortunately it turned out we can destroy servers, created by previous versions, as no tags were set there. To fix this situation we come back to the previous solution - deleting servers by metadata.
In openshift#3818 we introduced tag-based server delition. Unfortunately it turned out we can destroy servers, created by previous versions, as no tags were set there. To fix this situation we come back to the previous solution - deleting servers by metadata.
Now to delete servers we first get a list of all available servers from Nova, and then we iterate through them to find those with required metadata. In the case of a large number of servers, this can take a very long time.
Fortunately gophercloud introduced filtering by tags, so we can start using this feature to get only servers with the required tag.
gophercloud/gophercloud#1759