Bug 743562 - undefined method `name' for nil:NilClass when clicked on view deployable definition( for multi instance)
Summary: undefined method `name' for nil:NilClass when clicked on view deployable defi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-05 11:47 UTC by Aziza Karol
Modified: 2012-05-15 22:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:10:32 UTC


Attachments (Terms of Use)
error for multi instance deployable def (211.94 KB, image/png)
2011-10-05 11:48 UTC, Aziza Karol
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Aziza Karol 2011-10-05 11:47:05 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.create a deployable definition for multiple instance.
2.navigate to new deployment and create a deployment with the below deployment definition.
3.click on View deployable definition

undefined method `name' for nil:NilClass  is displayed.
see attach screenshot.


deployable definition file:

<deployable name="aziza">
<description>This is an example deployment</description>
<assemblies>
<assembly name="frontend1" hwp="hwp1">
<image id="34cfafde-132a-4d15-aee2-8641058c1da9" build="ca465fee-c714-4a02-94fc-abaa270fed7c">
</image>
</assembly>
<assembly name="frontend2" hwp="hwp1">
<image id="34cfafde-132a-4d15-aee2-8641058c1da9" build="ca465fee-c714-4a02-94fc-abaa270fed7c">
</image>
</assembly>
</assemblies>
</deployable>

  


Additional info:
[root@dell-per905-01 server]# rpm -qa | grep aeolus
aeolus-all-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-conductor-doc-0.4.0-0.20111003184622git65a7d19.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-configure-2.0.2-4.20110930103205gitaf78594.fc15.noarch
aeolus-conductor-daemons-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-conductor-0.4.0-0.20111003184622git65a7d19.fc15.noarch

Comment 1 Aziza Karol 2011-10-05 11:48:16 UTC
Created attachment 526474 [details]
error for multi instance deployable  def

Comment 3 chris alfonso 2011-10-05 18:58:50 UTC
This seemed to work fine for me, I was able to see the two images defined in the deployable when I used the view link.  Then I launched them, and it just worked. Would you mind upgrading and try again? 

rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-conductor-daemons-0.4.0-0.20111004192348git2cf5ee6.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
aeolus-configure-2.0.2-4.20110930103205gitaf78594.fc15.noarch
aeolus-conductor-doc-0.4.0-0.20111004192348git2cf5ee6.fc15.noarch
aeolus-conductor-0.4.0-0.20111004192348git2cf5ee6.fc15.noarch
aeolus-all-0.4.0-0.20111004192348git2cf5ee6.fc15.noarch

Comment 4 Aziza Karol 2011-10-10 05:41:21 UTC
The above error is not observed now.

Able to see the two images defined in
the deployable view link.

verified on:
[root@dell-pesc430-03 templates]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-conductor-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-all-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch
[root@dell-pesc430-03 templates]#

Comment 6 errata-xmlrpc 2012-05-15 22:10:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html


Note You need to log in before you can comment on or make changes to this bug.