Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1340570 - Service :Orchestration : Orchestration service request fail for Ec2
Service :Orchestration : Orchestration service request fail for Ec2
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.6.0
Assigned To: Bill Wei
Shveta
ec2:stack:provision
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-27 19:11 EDT by Shveta
Modified: 2016-07-19 10:14 EDT (History)
6 users (show)

See Also:
Fixed In Version: 5.6.0.10
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-29 12:06:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
logs (3.07 MB, text/plain)
2016-05-27 19:11 EDT, Shveta
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description Shveta 2016-05-27 19:11:29 EDT
Created attachment 1162563 [details]
logs

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Create an orchestration service request for ec2. 
2. request fails with error . logs attached.
3."unexpected value at params[:timeout] (MiqException::MiqOrchestrationProvisionError) "

Actual results:


Expected results:


Additional info:
Build : 5.6.0.8-rc1.20160524155303_f2a5a50
Comment 3 Bill Wei 2016-05-31 23:08:00 EDT
There were two bugs that failed the service provisioning. Please verify both scenarios.

1. Leave the timeout unfilled. Prior the fix error "unexpected value at params[:timeout]".

2. Give the timeout some valid number. Prior the fix error "unexpected value at params[:timeout]". 
Note the actual time when you get the error is longer than the timeout minutes because the provisioning has pre- and post-postvisioning steps. The provider also takes extra time to do the rollback after the normal stack creation times out.
Comment 4 CFME Bot 2016-06-01 12:05:52 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/d0c8a60af2c2675b3a8d97f492ed7c64fd40be93

commit d0c8a60af2c2675b3a8d97f492ed7c64fd40be93
Author:     Bill Wei <bilwei@redhat.com>
AuthorDate: Tue May 31 17:10:48 2016 -0400
Commit:     Bill Wei <bilwei@redhat.com>
CommitDate: Tue May 31 17:10:55 2016 -0400

    Do not convert nil to 0 for automate_output_value
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1340570

 app/models/dialog_field_text_box.rb       |  1 +
 spec/models/dialog_field_text_box_spec.rb | 16 ++++++++++++++++
 2 files changed, 17 insertions(+)
Comment 5 CFME Bot 2016-06-01 12:05:57 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/ec0f6d52ebd98a649ff13b1874bd3396d0df9388

commit ec0f6d52ebd98a649ff13b1874bd3396d0df9388
Author:     Bill Wei <bilwei@redhat.com>
AuthorDate: Tue May 31 17:30:50 2016 -0400
Commit:     Bill Wei <bilwei@redhat.com>
CommitDate: Tue May 31 17:30:58 2016 -0400

    change timeout to timeout_in_minutes due to sdk 2.0 upgrade
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1340570

 .../amazon/cloud_manager/orchestration_service_option_converter.rb  | 2 +-
 spec/models/service_orchestration/option_converter_spec.rb          | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)
Comment 6 Shveta 2016-06-08 15:24:41 EDT
Fixed .
Verified in 5.6.0.10-rc2.1.20160607103248_d06c141
Comment 9 errata-xmlrpc 2016-06-29 12:06:39 EDT
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.

https://access.redhat.com/errata/RHBA-2016:1348

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