Bug 1296581
Summary: | Running a Control Action of "Invoke a Custom Automation" results in the error "MiqAeServiceModelBase.ar_method raised: <RuntimeError>: <user_id not specified in Automation request>" | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
Component: | Automate | Assignee: | Lucy Fu <lufu> |
Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.5.0 | CC: | bbilgin, cpelland, dajohnso, jhardy, lufu, mfeifer, mkanoor, nachandr, obarenbo, pmcgowan, snansi, tfitzger |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.5.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.5.2.1 | Doc Type: | Bug Fix |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | 1296122 | Environment: | |
Last Closed: | 2016-02-10 15:31:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1296122 | ||
Bug Blocks: |
Comment 2
CFME Bot
2016-01-12 01:27:24 UTC
Verified in 5.5.2.1 Verified that custom automation is successfully run when it's defined as a Control Policy action. 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:0159 |