Bug 604790

Summary: deploy wizard version selector is disabled
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: ProvisioningAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED CURRENTRELEASE QA Contact: Sunil Kondkar <skondkar>
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.0.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 2.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-12 16:46:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 577210    
Attachments:
Description Flags
Image showing disabled version selector in deploy wizard none

Description John Mazzitelli 2010-06-16 18:11:00 UTC
Created attachment 424542 [details]
Image showing disabled version selector in deploy wizard

Description of problem:

Cannot deploy a bundle because the deploy wizard has the version selector disabled (i.e. cannot select any version).

How reproducible:

1, Start with a clean database (I've seen it where this problem does not occur after you've already put bundles in the database).

2. start agent, import ant bundle handler in inventory and ceate any group of platforms

3. Go to Bundles GUI and click "New" to go to Create Wizard and upload any bundle distribution file.

4. Go to Bundles List view and click on the new bundle you uploaded, this takes you do the Bundle view, there should be a "delete" and "deploy" button on the right side

5. Click Deploy button to get to the Deploy wizard

6. Enter information about the destination, pick your group and enter any directory

7. Once you get to the step that asks for the bundle version to deploy, notice the version selector is greyed out (see attached image). You can't go any further now and you can't deploy.

Comment 1 Jay Shaughnessy 2010-06-21 17:59:39 UTC
This looks like a timing issue.  The getDestinationStep gathers dest info and then creates the destination.  That destination is expected to exist in the next step, SelectBundleVersionStep.  If the async destination create did not complete fast enough it could cause the problem described.

fixing...

Comment 2 Jay Shaughnessy 2010-06-21 18:59:24 UTC
fix commit: e24f75a56fa6dabe7ee32216dd5d27b83c1e8834

Comment 3 Sunil Kondkar 2010-06-25 10:55:49 UTC
Verified on JON 2.4 GA_QA build#42

Uploaded a bundle distribution file(No bundles preexist in the database), navigated to Deploy wizard, entered destination and group information. Clicking on 'Next' button asks for the bundle version to deploy. 

The screen displays two options below:
Latest Version [ 1.0 ]
Select Version from List:

If user selects the option 'Select Version from List:', user can choose the version from the dropdown 'Deployment Version'.
User can proceed further steps like 'setting deployment configuration', provide deploy information'.

Comment 4 Corey Welton 2010-08-12 16:46:57 UTC
Mass-closure of verified bugs against JON.