Bug 1720212 - Service reconfigure failed with error "Service Reconfigure failed"
Summary: Service reconfigure failed with error "Service Reconfigure failed"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.10.6
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.11.0
Assignee: William Fitzgerald
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1727970
TreeView+ depends on / blocked
 
Reported: 2019-06-13 12:05 UTC by Niyaz Akhtar Ansari
Modified: 2019-12-13 15:01 UTC (History)
5 users (show)

Fixed In Version: 5.11.0.14
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1727970 (view as bug list)
Environment:
Last Closed: 2019-12-13 15:01:18 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
error (151.97 KB, image/png)
2019-06-13 12:05 UTC, Niyaz Akhtar Ansari
no flags Details
evm and automation log (7.67 MB, application/x-tar)
2019-06-14 06:29 UTC, Niyaz Akhtar Ansari
no flags Details

Description Niyaz Akhtar Ansari 2019-06-13 12:05:22 UTC
Created attachment 1580261 [details]
error

Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1. Add a heat template (Service - Orchestration template- heat template - Add)
2. Create a service dialog from that template (Service - Orchestration - select template - create dialog)
3. Create a catalog item for type "Orchestration". Provider "RHOS7-GA" selected 
4. Select template and dialog created above
5. Order service catalog.
6. Go to My service -> select the service and reconfigure it


Actual results:
1. Once submitted, page do not navigate to request page
2. Request raised is not automatically approved
3. Request fails After sometime when approving the service 

Expected results:
1. Page should naviagte to request page after request submitted
2. Request should be auto approved
3. It should works


Additional info:

Comment 2 Greg McCullough 2019-06-13 16:30:17 UTC
Are there any errors in the log that could help narrow down this issue?

Comment 3 Niyaz Akhtar Ansari 2019-06-14 06:29:04 UTC
Created attachment 1580543 [details]
evm and automation log

Comment 4 William Fitzgerald 2019-06-24 15:46:44 UTC
Request looks like it tried 100 times and failed


[----] E, [2019-06-14T02:23:06.410559 #12311:3fef58] ERROR -- : Q-task_id([r2_service_reconfigure_task_2]) State=<checkreconfigured> running  raised exception: <number of retries <101> exceeded maximum of <100>>


Do you have a reproducer?

Comment 5 Niyaz Akhtar Ansari 2019-06-25 13:40:31 UTC
Right now trying to recreate it but due to some OSP infra issue I am not able to recreate the issue
I will provide the reproducer once the issue will fixed.

Comment 6 Tina Fitzgerald 2019-07-01 20:17:07 UTC
Hi Niyaz,

Do you think you'll have the problem resolved soon?
The GA build is in one week, and we'll need the reproducer to move forward with our investigation?

Thanks,
Tina

Comment 9 CFME Bot 2019-07-08 16:55:53 UTC
New commit detected on ManageIQ/manageiq-content/master:

https://github.com/ManageIQ/manageiq-content/commit/737b0933c96ce01454915c13914a4d3d80af8ebc
commit 737b0933c96ce01454915c13914a4d3d80af8ebc
Author:     Tina Fitzgerald <tfitzger>
AuthorDate: Fri Jul  5 16:22:54 2019 -0400
Commit:     Tina Fitzgerald <tfitzger>
CommitDate: Fri Jul  5 16:22:54 2019 -0400

    Reset ae_reason and ae_result in check_refreshed when
    refresh_may_have_completed is true.

    The update_result and update_reason state_vars contained the
    previous values.  The state_var update_result
    value was still set to retry from the previous execution which caused
    the state machine to retry instead of proceeding to the next state.
    It had another side affect in that the retry was set with no retry
    interval which caused the state machine to retry immediately instead of
    waiting the usual time interval.

    Resetting those values caused the state machine to progress to the next
    state and complete successfully.

    Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1720212

 content/automate/ManageIQ/Cloud/Orchestration/Reconfiguration/StateMachines/Methods.class/__methods__/check_reconfigured.rb | 6 +-
 spec/content/automate/ManageIQ/Cloud/Orchestration/Reconfiguration/StateMachines/Methods.class/__methods__/check_reconfigured_spec.rb | 6 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

Comment 11 Niyaz Akhtar Ansari 2019-07-31 11:16:25 UTC
Verfied in Version 5.11.0.17.20190730152352_93b1c30


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