Bug 1067735

Summary: [oVirt] [Fix] Changes in selected template does not update the OS list
Product: [Retired] oVirt Reporter: gustavo.pedrosa
Component: ovirt-engine-webadminAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: ahadas, ecohen, gchaplik, gklein, gustavo.pedrosa, iheim, leonardo.bianconi, lsvaty, mgoldboi, michal.skrivanek, ofrenkel, rbalakri, rgolan, vdelima, vitor.lima, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: ppc64   
OS: Linux   
Whiteboard: virt
Fixed In Version: ovirt-3.5.0-alpha1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:43:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description gustavo.pedrosa 2014-02-21 00:17:44 UTC 
Description of problem:
This fix forces an OS list update in the "New Pool" and the
"Edit Pool" dialogs after the user selects a template. It was
introduced in order to avoid a class of bugs where the OS list
could show OSes for another architecture during the creation or
edition of VM Pools.

Version-Release number of selected component (if applicable):
ovirt-engine-3.4

How reproducible:
100%

Steps to Reproduce:
1. Just open the New Pool dialog
2.
3.

Actual results:
Does not update the OS list

Expected results:
Update the OS list

Additional info:
Comment 1 Itamar Heim 2014-02-23 08:28:32 UTC 
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.
Comment 2 Sandro Bonazzola 2014-03-04 09:29:17 UTC 
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 3 Michal Skrivanek 2014-05-07 13:07:55 UTC 
fix is merged to 3.5.
the 3.4 patch is outstanding for quite a long time and it may be a bit complicated to rebase now…I'd propose to keep this 3.5 only (IOW close as MODIFIED)
what do you think?
Comment 4 gustavo.pedrosa 2014-05-07 14:03:00 UTC 
@Michal, OK, no problema. Thank you very much indeed.
Comment 5 Lukas Svaty 2014-07-31 12:52:03 UTC 
verified in ovirt-3.5.0-beta2
Comment 6 Sandro Bonazzola 2014-10-17 12:43:37 UTC 
oVirt 3.5 has been released and should include the fix for this issue.