Bug #13595
closed
Storage domain dropdown menu doesn't work
Description
Dear support team
when I try to create a new VM with foreman on oVirt I cannot able to select an storage domain from the dropdown menu because it doesn't work.
As you can see from the next image if I select the dropdown menu nothing is displayed
Viewing the source code I found 2 elements for the dropdown menu, asu you can see from the next image:
If I delete the first element and remove "display: none" from the style parameter, as you can see in the next image:
Al works fine, as you can see in the next image:
Best regards
Diego
Files
| code_right.png | View code_right.png | 15.7 KB | |||
| storage_domain_ok.png | View storage_domain_ok.png | 19.6 KB | |||
| code_wrong.png | View code_wrong.png | 19.5 KB | |||
| storage_domain_broken.png | View storage_domain_broken.png | 14.7 KB |
Updated by Dominic Cleal about 8 years ago
- Category changed from Web Interface to Compute resources - oVirt
- Priority changed from Urgent to Normal
Updated by Doina Cristina Aiftimiei about 8 years ago
Same problem here and is... blocking.
Working with workarounds is not a clean way to go.
Updated by Ben Bettridge about 8 years ago
If you view a host that already has disks attached to it, then the form works correctly. Might indicate that the issue is in whatever code generates the form on the page.
Had a look through the code, but I can't really make heads or tails of where this all happens.
Updated by Ben Bettridge about 8 years ago
Dug through it some more. At runtime the template is generated correctly (without the extra div), but on the page it is stored incorrectly in the DOM. It appears not to be an issue with the template generation, but instead with what ever process is adding it to the DOM, under children_fields. This is a pretty critical bug because it more or less prevents people from building out virtual machines - is anyone else looking at it?
This bug impacts VMWare Plugin, oVirt Plugin and a version of the Xen Plugin.
Updated by Diego Michelotto about 8 years ago
The bug still exist in the 1.10.2 release.
Regards
Diego
Updated by Angelo Lisco about 8 years ago
Unluckily, even if the foreman interface was migrated to Patterfly, the bug is still present in 1.11RC1 release.
I think this should be fixed before 1.11 GA.
Updated by Anonymous about 8 years ago
- translation missing: en.field_release set to 71
As this seems to be a general bug that's hitting multiple compute resource types, somebody should have a look.
Updated by David Rom about 8 years ago
- Related to Bug #14041: VM provisioning : dropdown lists greyed out in new volume fields added
Updated by Dominic Cleal about 8 years ago
- Status changed from New to Duplicate
- translation missing: en.field_release deleted (
71)
This should be fixed by the changes under ticket #14041, which are currently in review and anticipated to be included in 1.10.3. This means they will probably be in 1.11.0 too, depending on the timing. Thanks for the report!