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

Missing Boot Order options on Fireedge GUI for VM instances #6757

Closed
3 tasks
ibrahimkahn opened this issue Oct 16, 2024 · 0 comments · Fixed by OpenNebula/docs#3125
Closed
3 tasks

Missing Boot Order options on Fireedge GUI for VM instances #6757

ibrahimkahn opened this issue Oct 16, 2024 · 0 comments · Fixed by OpenNebula/docs#3125

Comments

@ibrahimkahn
Copy link

Description
The Fireedge web interface does not display Boot Order options for virtual machine instances, whether they are running or powered off. However, these options are available under the Templates context menu.

To Reproduce
Steps to reproduce the behavior.

-Download an image from marketplace,
-Create a template for the instance with two or more disks,
-Instantiate a VM instance,
-Go to VM Configuration > Update VM Configuration.

Expected behavior
The Boot Order options should be available for VM instances, just as they are in the Ruby-based Sunstone for oneadmin or other group accounts. This feature helps users change the boot disk after OS or application installation.

Details

  • Affected Component: Fireedge GUI
  • Hypervisor: KVM/QEMU
  • Version: 6.10.0
  • Account: oneadmin
  • View: admin

Screenshots

Fireedge
Boot Order options missing under OS/CPU > Boot
no_boot_order_fsunstone

Sunstone
Boot Order options present in current version
boot_order_rsunstone

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@tinova tinova added this to the Release 6.10.1 milestone Oct 17, 2024
vichansson added a commit to OpenNebula/docs that referenced this issue Dec 11, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
@vichansson vichansson linked a pull request Dec 11, 2024 that will close this issue
2 tasks
tinova added a commit to OpenNebula/docs that referenced this issue Dec 11, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
Co-authored-by: Tino Vázquez <cvazquez@opennebula.io>
@tinova tinova closed this as completed Dec 11, 2024
@tinova tinova reopened this Dec 11, 2024
vichansson added a commit to OpenNebula/docs that referenced this issue Dec 20, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
tinova pushed a commit to OpenNebula/docs that referenced this issue Dec 20, 2024
Signed-off-by: Victor Hansson <vhansson@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.

6 participants