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

Hypervisor selection option disappears under template creation when using KVM view. #3435

Closed
7 tasks
sergiojvg opened this issue Jun 17, 2019 · 0 comments
Closed
7 tasks

Comments

@sergiojvg
Copy link
Contributor

Description
The option to select the hypervisor type on the template creation wizard disappears when using KVM admin view. Although is pointless to select vcenter hypervisor under kvm view, LXD is not.

DeepinScreenshot_select-area_20190617184951

No option from the view explains that behavior.

root@orchestrator1:/etc/one/sunstone-views# diff kvm/admin.yaml mixed/admin.yaml 
68,70d67
<     # True to show the host datatable to instantiate VM
<     show_host_instantiate: true
< 
76a74,76
>     # True to show the host datatable to instantiate VM
>     show_host_instantiate: true
> 
79c79
<     vcenter_vm_folder: false
---
>     vcenter_vm_folder: true
246c246
<             Template.import_dialog: false
---
>             Template.import_dialog: true
495a496,497
>             VirtualRouter.lockU: true
>             VirtualRouter.unlock: true
601c603
<             Datastore.import_dialog: false
---
>             Datastore.import_dialog: true
636c638
<             Image.import_dialog: false
---
>             Image.import_dialog: true
775c777,778
<             Network.import_dialog: false
---
>             Network.instantiate_dialog: true
>             Network.import_dialog: true

To Reproduce
Try to get the option to select different hypervisors under the KVM admin view.

Details

  • Affected Component: Sunstone
  • Version: 5.8.1

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@tinova tinova added this to the Release 5.10 milestone Jun 18, 2019
jloboescalona2 pushed a commit to jloboescalona2/one that referenced this issue Jul 18, 2019

Verified

This commit was signed with the committer’s verified signature.
chaudum Christian Haudum
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
tinova pushed a commit that referenced this issue Jul 18, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
tinova pushed a commit that referenced this issue Jul 18, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
(cherry picked from commit ed9d64c)
@tinova tinova closed this as completed Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants