Back to bug 1296581

Who When What Removed Added
John Prause 2016-01-07 15:36:17 UTC Keywords ZStream
Status NEW ASSIGNED
Target Release 5.6.0 5.5.2
Assignee gmccullo lufu
Chris Pelland 2016-01-08 18:33:45 UTC Severity medium high
Nandini Chandra 2016-01-08 23:31:10 UTC CC nachandr
Lucy Fu 2016-01-12 14:33:43 UTC Status ASSIGNED POST
John Prause 2016-01-12 14:57:42 UTC Status POST MODIFIED
Marianne Feifer 2016-01-13 15:20:49 UTC CC mfeifer
Doc Text Cause: user_id, miq_group_id and tenant_id are required in Automation request.

Consequence: Running a Control Policy that contains an action type of "Invoke a Custom Automation" always fails, with the error "user_id not specified in Automation request"

Fix: Pass along user_id, miq_group_id and tenant_id in Automation request.

Result: Invocation is successful.
errata-xmlrpc 2016-01-14 20:31:05 UTC Status MODIFIED ON_QA
John Prause 2016-01-14 21:33:17 UTC Fixed In Version 5.5.2.1
Shikha 2016-01-18 06:34:05 UTC CC snansi
Doc Text Cause: user_id, miq_group_id and tenant_id are required in Automation request.

Consequence: Running a Control Policy that contains an action type of "Invoke a Custom Automation" always fails, with the error "user_id not specified in Automation request"

Fix: Pass along user_id, miq_group_id and tenant_id in Automation request.

Result: Invocation is successful.
In the previous version of CloudForms Management Engine, running a control policy containing an action type that invoked a custom automation always failed with an error that the user_id was not specified in the automation request. This error was caused by missing user id, miq_group_id and tenant_id arguments in the automation request. This bug was fixed by passing the missing user_id, miq_group_id and tenant_id arguments in the automation request. Invoking a custom automation now works as expected in the new version of CloudForms Management Engine.
dajohnso 2016-01-18 12:53:16 UTC QA Contact dajohnso nachandr
Birol Bilgin 2016-01-21 11:45:32 UTC CC bbilgin
Nandini Chandra 2016-01-22 17:23:59 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-02-10 15:31:17 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2016-02-10 10:31:17 UTC

Back to bug 1296581