Description of problem: There's an unhandled empty array case in a patch recently submitted. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: undefined method `>=' for []:Array Expected results: silently skip an empty array Additional info:
Any eta on a fix for this?
Ugh, hitting this now when trying out master. It's completely breaking deployables. Can't get into any screen for launching them. :( Screenshots attached.
Created attachment 598010 [details] Error when creating deployable from image.
Created attachment 598011 [details] Error when trying to get to a launch page.
Created attachment 598012 [details] Error when trying to launch via Monitor tab page.
Hitting this issue. Not able to create deployables and hence launch instances.
A short term workaround, just so you can get instances to launch (from jprovazn): ********************************* ********************************* diff --git a/src/app/models/deployable.rb b/src/app/models/deployable.rb index 9c6aff9..cc734ad 100644 --- a/src/app/models/deployable.rb +++ b/src/app/models/deployable.rb @@ -192,7 +192,7 @@ class Deployable < ActiveRecord::Base deployable_errors << "#{assembly_hash[:name]}: " + I18n.t('deployables.error.attribute_not_exist') end assemblies_array << assembly_hash - audrey_error = check_audrey_api_compatibility(image, assembly) + audrey_error = nil #check_audrey_api_compatibility(image, assembly) deployable_errors << "#{assembly_hash[:name]}: " + audrey_error if not audrey_error.nil? end [assemblies_array, images, missing_images, deployable_errors] ********************************* ********************************* This workaround lets the deployables page be shown here, single instances launch. Getting automatic failures with Audrey deployables, but that might be something else. (no idea)
pushed to master as d67759c127f44bf8b59ada0445a05273090e60a8
Just for clarity, the patch Dan pushed is a real working one, not the above "dodgy workaround" approach.
Application can be launched perfectly via monitor tab,create deployable from image as well as via launch page Verified on:- [root@dhcp201-113 ~]# rpm -qa|grep aeolus aeolus-conductor-doc-0.13.7-1.el6cf.noarch aeolus-all-0.13.7-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-0.13.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.7-1.el6cf.noarch
Created attachment 613660 [details] application launch success
CloudForms-1.1 shipped with aeolus-conductor-0.13.24-1.el6cf.src.rpm Marking this bug CLOSED CURRENTRELEASE. Please reopen if the problem has not been addressed in the 1.1 product.