Skip to content

vm created by ISO cannot resize the root disk size #4827

Closed

Description

@div8cn
ISSUE TYPE
  • Bug Report
COMPONENT NAME

CLOUDSTACK VERSION
4.15.0.0
CONFIGURATION
OS / ENVIRONMENT
SUMMARY

VM created by ISO cannot resize the root disk size.
Error:
Failed to resize Root volume. The service offering of this Volume has been configured with a root disk size; on such case a Root Volume can only be resized when changing to another Service Offering with a Root disk size. For more details please check out the Official Resizing Volumes documentation.

VM created by tempalte can resize root disk size.

#4341

My serviceoffering not set rootdisksize item

STEPS TO REPRODUCE
1. Create serviceoffering, name=iso-1c-1g, (do not set rootdisksize.)
2. Deploy the VM using ISO, name=iso-vm01, and use serviceoffering=iso-1c-1g.
3.stop vm iso-vm01.
4.resize iso-vm01 root disk size to 100G(size=120&id=ebe7be07-5276-4e38-8563-64d47ae83972&command=resizeVolume&response=json)

EXPECTED RESULTS
vm root disk size changed to 120G
ACTUAL RESULTS
Task execution failed
The root disk size has not changed.

API throws an error:
Failed to resize Root volume. The service offering of this Volume has been configured with a root disk size; on such case a Root Volume can only be resized when changing to another Service Offering with a Root disk size. For more details please check out the Official Resizing Volumes documentation.

Activity

  1. added this to the 4.15.1.0 milestone on Mar 17, 2021
  2. yadvr commented on Mar 17, 2021

    @yadvr
    Member

    @Pearl1594 can you check if your PR/fix addresses the case of ISO?

  3. Pearl1594 commented on Mar 17, 2021

    @Pearl1594
    Contributor

    @rhtyd I've added a fix to allow resizing of Root volume of a VM deployed from an ISO - 1c3fc3c.

  4. div8cn commented on Mar 17, 2021

    @div8cn
    ContributorAuthor

    I verified the commit 1c3fc3c

    It solved the problem.

    thank @Pearl1594 @rhtyd

  5. yadvr commented on Mar 18, 2021

    @yadvr
    Member

    @Pearl1594 is that commit part of your PR or already merged?

  6. Pearl1594 commented on Mar 18, 2021

    @Pearl1594
    Contributor

    It's part of PR #4829 - which hasn't yet been merged. Would you prefer me raising a separate PR to fix this? @rhtyd

  7. yadvr commented on Mar 30, 2021

    @yadvr
    Member

    Fixed in #4829

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions