-
Notifications
You must be signed in to change notification settings - Fork 1.3k
volume resize: Fix issue with volume resize on VMWare (deploy as-is templates) #4829
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 |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✖️ centos7 ✖️ centos8 ✖️ debian. SL-JID 138 |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✖️ centos7 ✖️ centos8 ✔️ debian. SL-JID 140 |
|
@blueorangutan package |
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✔️ centos7 ✖️ centos8 ✔️ debian. SL-JID 141 |
nvazquez
left a comment
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.
Looks good - perhaps also adding a check on the resizevolume and fail with a message when the volume is created from a deploy-as-is template?
| for (DiskTO vol : sortedDisks) { | ||
| if (vol.getType() == Volume.Type.ISO || deployAsIs && vol.getType() == Volume.Type.ROOT) { | ||
| rootDiskTO = vol; | ||
| resizeRootDiskOnVMStart(vmMo, rootDiskTO, hyperHost, context); |
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.
@Pearl1594 is this required for ISO as well?
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.
Thanks @sureshanaparti It's not required for ISO , have made the necessary change.
@nvazquez added checks to see if a compute offering with root disk size mentioned is used / overriding root disk size is attempted when deploying a vm with deploy as-is template and will accordingly throw an exception. |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✔️ centos7 ✖️ centos8 ✖️ debian. SL-JID 156 |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✖️ centos7 ✔️ centos8 ✔️ debian. SL-JID 158 |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 160 |
|
@blueorangutan test matrix |
|
@Pearl1594 a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests [S] |
|
@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 208 |
|
@blueorangutan test matrix |
|
@Pearl1594 a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
|
Trillian test result (tid-227)
|
|
Trillian test result (tid-228)
|
|
Trillian test result (tid-229)
|
sureshanaparti
left a comment
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.
code LGTM
|
Tests LGTM |
|
With @shwstppr to manually test it |
shwstppr
left a comment
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.
Tested on VMware 65u2 env. Works fine.
UI disables Root disk resize option for newly registered templates unlike earlier where it was shown but not honoured.
Earlier

Now

- Root volume resize of stopped VM deployed with a newly registered template (deployasis) - Successful
- Root volume resize of stopped VM deployed with an ISO - Successfull
shwstppr
left a comment
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.
While volume resize behaviour works for most cases CKS cluster noderootdisksize is not working as expected. Will need similar changes from f5e866c
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 267 |
|
@blueorangutan test centos7 vmware-67u3 |
|
@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
shwstppr
left a comment
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. Tested CKS node root disk resize with latest changes
Description
This PR fixes the issue pertaining to volume resize on VMWare for deploy as-is templates. VMware deploy as-is templates are those that are deployed as per the specification in the imported OVF. Hence override root disk size will not be adhered to for such templates. Moreover, when we deploy VMs in stopped state and resize the volume, the root disk doesn't get resized but the volume size is merely updated in the DB.
This PR also includes the following (for deploy as-is templates):
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Prior to the fix:
Deployed a VM in stopped state, resized volume from 3GB to 8GB

While the UI shows that the Volume is resized, the root volume inside the VM doesn't seem to have gotten resized:

Post fix
Deployed a VM in stopped state, resized the volume from 3GB to 8GB

Notice that the volume size as shown in the UI complies with the value inside the VM
Or verify the same on vcenter