Skip to content

migrateVolume does not copy the template #5759

Closed
Closed
migrateVolume does not copy the template#5759
Assignees
gp-santos
Labels
Severity:Majorcomponent:migrationcomponent:primary-storagecomponent:storagecomponent:templatesstatus:staletype:bugtype:enhancement
Milestone
4.19.1.0

Description

@GutoVeronezi
GutoVeronezi
opened on Dec 8, 2021

When a volume is copied to another storage pool, if the template does not exist in the destination storage pool yet, it should be copied. The API migrateVirtualMachineWithVolume already does it; however, when migrating the volume with migrateVolume (VM stopped), the template is not copied, which causes inconsistencies in the database and primary storage systems.

Activity

  1. DaanHoogland commented on Dec 9, 2021

    @DaanHoogland
    DaanHoogland
    on Dec 9, 2021
    Contributor

    is this what you are fixing in #5758, @GutoVeronezi ? or do you mean that more improvement is needed after that?

  2. GutoVeronezi commented on Dec 9, 2021

    @GutoVeronezi
    GutoVeronezi
    on Dec 9, 2021
    ContributorAuthor

    @DaanHoogland it will need more improvement after that.

  3. nvazquez commented on Feb 4, 2022

    @nvazquez
    nvazquez
    on Feb 4, 2022
    Contributor

    Hi @GutoVeronezi are you working on this issue or planning to?

  4. nvazquez
    added
    component:migration
    type:enhancement
    on Feb 4, 2022

  5. GutoVeronezi commented on Feb 4, 2022

    @GutoVeronezi
    GutoVeronezi
    on Feb 4, 2022
    ContributorAuthor

    Hi, @nvazquez, I have other priorities at the moment, this issue is not in my plannings for now.

  6. nvazquez commented on Feb 4, 2022

    @nvazquez
    nvazquez
    on Feb 4, 2022
    Contributor

    Thanks for clarifying @GutoVeronezi

  7. nvazquez
    added this to the 4.18.0.0 milestone on Mar 6, 2022
  8. nvazquez
    modified the milestones: 4.18.0.0, 4.17.1.0 on Apr 20, 2022

  9. shwstppr commented on Aug 18, 2022

    @shwstppr
    shwstppr
    on Aug 18, 2022
    Contributor

    Moving this to next milestone

  10. shwstppr
    modified the milestones: 4.17.1.0, 4.18.0.0 on Aug 18, 2022
  11. DaanHoogland
    added
    component:primary-storage
    component:templates
    on Aug 18, 2022

  12. 35 remaining items

  13. yadvr commented on Apr 30, 2024

    @yadvr
    yadvr
    on Apr 30, 2024
    Member

    Is this fixed ?

  14. yadvr
    added
    age:2years_plus
    status:stale
    on Apr 30, 2024

  15. DaanHoogland commented on May 31, 2024

    @DaanHoogland
    DaanHoogland
    on May 31, 2024
    Contributor

    @gpordeus (cc @GutoVeronezi ) is work going on on this?

  16. DaanHoogland
    modified the milestones: 4.18.3, 4.19.1.0 on May 31, 2024
  17. sureshanaparti
    added this to Apache CloudStack BugFest - Issueson Jun 3, 2024
  18. sureshanaparti
    moved this to Todo in Apache CloudStack BugFest - Issueson Jun 3, 2024
  19. sureshanaparti
    added this to Apache CloudStack 4.19.1on Jun 7, 2024

  20. gp-santos commented on Jun 11, 2024

    @gp-santos
    gp-santos
    on Jun 11, 2024
    Collaborator

    @DaanHoogland @rohityadavcloud @GutoVeronezi

    I tried reproducing the problem with the latest main, in an ubuntu+kvm environment, but wasn't able to.

    Any missing template inconsistencies with migrateVirtualMachineWithVolume should be solved by #8911, since it standardizes always merging the backing file into the volume.

    As for migrateVolume:

    • Deployed a VM, its volume on NFS primary storage. It went up with the backing file. I stopped the VM, migrated the volume to SMP primary storage and it resulted in a merged backing file.
    scc@local:/mnt/pri-storage-smp$ qemu-img info 9eb27ca6-d721-45f0-a334-144e29377fc5 
image: 9eb27ca6-d721-45f0-a334-144e29377fc5
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 3.09 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
    • Deployed another VM with a new template, its volume on NFS primary storage. It went up with the backing file. I stopped the VM, migrated the volume to another NFS primary storage and it resulted in a merged backing file.
    scc@local:/mnt/a548af6a-abff-3541-8130-bfe19ff1cb7d$ qemu-img info 8daf78fe-202b-481d-93c9-aa1299dd43b9
image: 8daf78fe-202b-481d-93c9-aa1299dd43b9
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
    • Deployed another VM with yet another template, its volume on local storage. I stopped the VM, migrated the volume to another local storage and it resulted in a merged backing file. Started the VM back up and migrated it and its volume back to the first local storage. The VM ran normally, its volume without any mention of a backing file.
    scc@host-local:/var/lib/libvirt/images$ qemu-img info -U 1bbcd0df-747d-4bfd-9680-b8dff1f1a97e
image: 1bbcd0df-747d-4bfd-9680-b8dff1f1a97e
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
    • Deployed another VM with the same template as last test, its volume on local storage. I stopped the VM, migrated the volume to another local storage that already had the same template and it resulted in a merged backing file. Started the VM back up and migrated it and its volume back to the first local storage. The VM ran normally, its volume without any mention of a backing file.
    scc@local:/var/lib/libvirt/images$ qemu-img info -U d8dd43db-f798-404e-9de1-0914308c8cd0
image: d8dd43db-f798-404e-9de1-0914308c8cd0
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
backing file: /var/lib/libvirt/images/318bc978-1e0f-4ab2-8b04-7fad5dc183cd
backing file format: qcow2
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false

    The local storage problem looks the same as #7942 and seem to have been solved by #7945.

  21. DaanHoogland commented on Jun 12, 2024

    @DaanHoogland
    DaanHoogland
    on Jun 12, 2024
    Contributor

    ok @gpordeus , I am not sure if you can, but if so feel free to close the issue unless you feel more discussion is needed. We can then convert this ticket to a discussion.

  22. gp-santos
    closed this as completedon Jun 12, 2024
  23. github-project-automation
    moved this from Todo to Done in Apache CloudStack BugFest - Issueson Jun 12, 2024
  24. github-project-automation
    moved this to Done in Apache CloudStack 4.19.1on Jun 12, 2024
  25. DaanHoogland
    removed this from Apache CloudStack BugFest - Issueson Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Severity:Majorcomponent:migrationcomponent:primary-storagecomponent:storagecomponent:templatesstatus:staletype:bugtype:enhancement

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions