Bug 767788

Summary: New Deployment from Monitor pool list results in - The record you tried to access does not exist, it may have been deleted
Product: [Retired] CloudForms Cloud Engine Reporter: James Laska <jlaska>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, jturner, ssachdev
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-15 15:41:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
expected result
none
actual result
none
demonstration screencast -- Ogg data, OGM video (DivX 5) none

Description James Laska 2011-12-14 21:21:59 UTC
Created attachment 546904 [details]
expected result

Description of problem:

Attempting to launch a deployment results in error, "The record you tried to access does not exist, it may have been deleted"

Version-Release number of selected component (if applicable):
 * aeolus-all-0.7.0-4.fc15.src.rpm
 * aeolus-conductor-0.7.0-4.fc15.src.rpm
 * aeolus-configure-2.4.0-3.fc15.src.rpm
 * imagefactory-1.0.0rc1-1.fc15.src.rpm
 * iwhd-1.1-1.fc15.src.rpm
 * oz-0.7.9-4.fc15.src.rpm

How reproducible:
 * seems like every attempt to deploy using the procedure below fails

Steps to Reproduce:
1. In the conductor UI, click "Monitor"
2. Expand Default pool, and select 'New Deployment'
3. Supply a valid 'Deployment Name' and choose 'Load definition from XML' and select Next

  
Actual results:

Error message at the top of the screen indicates "The record you tried to access does not exist, it may have been deleted"

Expected results:

See attached screenshot generated by following the procedure:
 1. In the conductor UI, click "Monitor"
 2. In the catalog drop-down, select a valid catalog entry
 3. On the appropriate catalog entry, click 'Select'

Additional info:

Comment 1 James Laska 2011-12-14 21:24:32 UTC
Created attachment 546905 [details]
actual result

Comment 2 wes hayutin 2011-12-15 00:33:46 UTC
Either you have the wrong recreate or you may be using the mock provider...

You need to pick a realm.. but the workflow is..
Steps to Reproduce:
1. In the conductor UI, click "Monitor"
2. Expand Default pool, and select 'New Deployment'
3. Supply a valid 'Deployment Name' and choose 'Load definition from XML'
4. Select a realm from the drop down
5. click next

You can try on https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor
using deployable ce-elsrc, w/ us-east-1

Making realm a required field to select is a bug.. but a different bug.      Beaker Test information:
                         HOSTNAME=qeblade30.rhq.lab.eng.bos.redhat.com
                            JOBID=171142
                         RECIPEID=358412
                    RESULT_SERVER=127.0.0.1:7089
                           DISTRO=Fedora-15
                     ARCHITECTURE=x86_64
**  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **
[root@qeblade30 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.7.0-4.fc15.noarch
aeolus-configure-2.4.0-3.fc15.noarch
aeolus-all-0.7.0-4.fc15.noarch
rubygem-aeolus-cli-0.2.0-3.fc15.noarch
aeolus-conductor-0.7.0-4.fc15.noarch
rubygem-aeolus-image-0.2.0-1.fc15.noarch
aeolus-conductor-daemons-0.7.0-4.fc15.noarch

Comment 3 James Laska 2011-12-15 13:23:42 UTC
Please hold off on closing a bug until the reporter has had a chance to respond to any needinfo.  If it's PEBKAC, I'll be the first to apologize and close as NOTABUG.

(In reply to comment #2)
> Either you have the wrong recreate or you may be using the mock provider...
> 
> You need to pick a realm.. but the workflow is..
> Steps to Reproduce:
> 1. In the conductor UI, click "Monitor"
> 2. Expand Default pool, and select 'New Deployment'
> 3. Supply a valid 'Deployment Name' and choose 'Load definition from XML'
> 4. Select a realm from the drop down
> 5. click next

Regardless of the workflow, the error provided doesn't line up with the reproducer.  So worst case, if this involves bad input, there may be room to improve the error handling.  Or at the least, the documentation needs to be updated (http://aeolusproject.org/start_image.html).  

> You can try on https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor
> using deployable ce-elsrc, w/ us-east-1

Using the steps to reproduce provided in comment#0, or the steps you suggest in comment#2 (the difference being selection of a realm), I encounter the error.  Whether I choose a realm, or not, I get the same error on qeblade30 (and a third system used by funzo).

Comment 4 James Laska 2011-12-15 13:48:37 UTC
Created attachment 547248 [details]
demonstration screencast -- Ogg data, OGM video (DivX 5)

Perhaps my mistake is apparent in the attached screencast which shows both reproducers attempted on qeblade30

Comment 5 James Laska 2011-12-15 15:41:53 UTC
Appears the problem here is attempting to create a deployment while selecting a deployable value of "Load definition from XML".  It seems this is an invalid choice, and user-interface should prevent the user from submitting this value.  Form validation will be handled by bug#767842

*** This bug has been marked as a duplicate of bug 767842 ***