Skip to content
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

(GUI) VM template update does not modify IMAGE_ID #6895

Closed
3 tasks
sk4zuzu opened this issue Feb 4, 2025 · 0 comments · Fixed by OpenNebula/docs#3195
Closed
3 tasks

(GUI) VM template update does not modify IMAGE_ID #6895

sk4zuzu opened this issue Feb 4, 2025 · 0 comments · Fixed by OpenNebula/docs#3195

Comments

@sk4zuzu
Copy link
Contributor

sk4zuzu commented Feb 4, 2025

Description
When a VM template contains DISK = [ IMAGE_ID="2" ] and update is performed in FireEdge, then IMAGE_ID is never updated, instead FireEdge just adds IMAGE. All this makes the VM template unusable.

To Reproduce

  1. Download some VM template + image from marketplace (in GUI).
  2. Update the VM template and attach different image as the disk (in GUI).

Expected behavior
Either IMAGE_ID or IMAGE should exist (only one of them) and point to new image or both should be pointing to the new image correctly. 🤗

Details

  • Affected Component: FireEdge
  • Hypervisor: KVM
  • Version: 6.10.2

Additional context
🐈 + 🥒

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@dcarracedo dcarracedo self-assigned this Feb 5, 2025
@dcarracedo dcarracedo added this to the Release 6.10.3 milestone Feb 5, 2025
dcarracedo added a commit to OpenNebula/docs that referenced this issue Feb 7, 2025
Signed-off-by: dcarracedo <dcarracedo@opennebula.io>
@dcarracedo dcarracedo linked a pull request Feb 7, 2025 that will close this issue
2 tasks
@tinova tinova closed this as completed Feb 7, 2025
tinova pushed a commit to OpenNebula/docs that referenced this issue Feb 7, 2025
Signed-off-by: dcarracedo <dcarracedo@opennebula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants