[component-registry] incompatible logic isn’t same as for fuel-core components
Bug #1526353 reported by
Ruslan Khozinov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Andriy Popovych |
Bug Description
Fuel-build: 286
Example of component configuration:
- name: 'hypervisor:xen'
label: 'xen'
description: 'xen hyperviror'
compatible:
- name: 'hypervisor:
incompatible:
- name: 'hypervisor:vmware'
- name: ‘hypervisor:
When I’m checking a xen hypervisor checkbox, others checkboxes are not blocked.
But when I’m checking kvm checkbox, then qemu checkbox is blocked (and vice versa).
So, I think the logic of blocking of checkboxes should be the same for core components and for plugin components.
I mean, when we check a checkbox incompatible checkboxes should be blocked.
Changed in fuel: | |
assignee: | Partner Centric Engineering (fuel-partner-engineering) → Andriy Popovych (popovych-andrey) |
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
assignee: | Andriy Popovych (popovych-andrey) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Bulat Gaifullin (bgaifullin) → Andriy Popovych (popovych-andrey) |
tags: | added: area-pce-vcenter |
To post a comment you must log in.
From your description: 'hypervisor: libvirt: emu'. Is it mistake here in bug description or it's the same in your components metadata file? Valid option is 'hypervisor: libvirt: qemu'