-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[VMware] Added Worker VM tags for few cloned VMs while performing some volume operations. #5377
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
Conversation
@blueorangutan package |
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1021 |
@blueorangutan test centos7 vmware-67u3 |
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Trillian test result (tid-1781)
|
@sureshanaparti does this affect 4.15? If so please change PR branch to 4.15 esp for bugfixes, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
…e volume operations. Worker VM tags are missed for few cloned VMs in VMware, and so these are skipped when tracking / cleaning up of Worker VMs. Adding proper Worker VM tags to these VMs would make them trackable from CloudStack.
eafec0e
to
62b3c1b
Compare
@blueorangutan package |
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian. SL-JID 1059 |
@blueorangutan test centos7 vmware-67u3 |
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Trillian test result (tid-1836)
|
Description
Worker VM tags are missed for few cloned VMs in VMware, and so these are skipped when tracking / cleaning up of Worker VMs. Adding proper Worker VM tags to these VMs would make them trackable from CloudStack.
This PR updates the (missed) Worker VM tags for the cloned VMs (in VMware) when creating template from volume, and exporting volume to secondary storage.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
Snapshot operation (for detached disk) tasks in vCenter =>
Worker VM to attach disk =>
Cloned VM to export disk to secondary storage =>
How Has This Been Tested?
Manually verified the worker VM tags set in the cloned VMs (from vCenter) while performing the following operations.