Skip to content

Cannot upload root disc - convert datadisk to root disk #9758

Description

@AlexanderKgr
ISSUE TYPE
  • Bug Report
COMPONENT NAME
Uploading volume cannot be chosen as root disk. It is uploaded as datadisk and after that it is not possible to convert it to root disc
CLOUDSTACK VERSION
4.19.1.1
CONFIGURATION

Ubuntu 22.04 server edition

OS / ENVIRONMENT

Cloudstack 4.19.1.1 installed on ubuntu 22.04 server edition with xcp-ng as hypervisor

SUMMARY
STEPS TO REPRODUCE
Uploading volume cannot be chosen as root disk. It is uploaded as datadisk and after that it is not possible to convert it to root disc

{BB8825F7-4628-41F6-86EB-9D84CDBA6591}

{815F61C7-20B8-4B16-A3CC-2B3FD8A6D72C}

EXPECTED RESULTS
There could be an  option to select type of disc and it could have been uploaded as a root disc type
ACTUAL RESULTS
There is no option to select the type of the disc. Disc is uploaded as datadisk type and it is not possible to attach it to a vm.

Activity

  1. rajujith commented on Oct 3, 2024

    @rajujith
    Contributor

    @AlexanderKgr You can upload this file as a template? When you deploy an instance from template it gets copied to the desired ROOT volume.

  2. AlexanderKgr commented on Oct 3, 2024

    @AlexanderKgr
    Author

    @AlexanderKgr You can upload this file as a template? When you deploy an instance from template it gets copied to the desired ROOT volume.

    i don't want to create new instance. i just want to replace the volume. In previous versions of cloudstack it was possible.

  3. weizhouapache commented on Oct 10, 2024

    @weizhouapache
    Member

    @AlexanderKgr
    to be frank, I do not think it was possible to upload a volume as root disk, because the Uploaded volume is stored on secondary storage, it is not attached to any vm.

    you can try

    • attach the new volume to the vm as datadisk
    • if the vm is not running, start the vm and then stop it. The Uploaded volume will be copied from secondary storage to same storage pool as the root volume.
    • detach the new volume
    • detach the ROOT volume of the vm you want to replace
    • attach the new volume to the vm as ROOT disk (deviceId=0)
  4. locked and limited conversation to collaborators on Nov 8, 2024
  5. converted this issue into a discussion #9910 on Nov 8, 2024
  6. added this to the unplanned milestone on Sep 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions