Bug 1824846
Summary: | [RFE] make the ansible tower refresh worker continue on playbook import errors | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Felix Dewaleyne <fdewaley> |
Component: | Providers | Assignee: | Adam Grare <agrare> |
Status: | CLOSED ERRATA | QA Contact: | Jaroslav Henner <jhenner> |
Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | medium | ||
Version: | unspecified | CC: | agrare, dmetzger, fdewaley, jfrey, jhardy, jhenner, nachandr, nansari, obarenbo, simaishi |
Target Milestone: | GA | Keywords: | FutureFeature, Reopened, RFE, ZStream |
Target Release: | 5.11.6 | Flags: | pm-rhel:
cfme-5.11.z+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.11.6.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-10 15:56:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | Ansible | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1822318 |
Comment 5
CFME Bot
2020-04-22 19:56:06 UTC
New commit detected on ManageIQ/manageiq-providers-ansible_tower/jansa: https://github.com/ManageIQ/manageiq-providers-ansible_tower/commit/8f6c58b53a0e796fb513d3d40a905e052e53e82f commit 8f6c58b53a0e796fb513d3d40a905e052e53e82f Author: Gregg Tanzillo <gtanzill> AuthorDate: Wed Apr 22 19:53:53 2020 +0000 Commit: Gregg Tanzillo <gtanzill> CommitDate: Wed Apr 22 19:53:53 2020 +0000 Merge pull request #218 from agrare/bz_1824846_catch_parser_errors_on_individual_job_templates Catch exceptions when parsing job_templates (cherry picked from commit 3b0cb7bef5920127f112762c7a5183d95295f72e) https://bugzilla.redhat.com/show_bug.cgi?id=1824846 app/models/manageiq/providers/ansible_tower/inventory/parser/automation_manager.rb | 50 +- 1 file changed, 30 insertions(+), 20 deletions(-) New commit detected on ManageIQ/manageiq-providers-ansible_tower/ivanchuk: https://github.com/ManageIQ/manageiq-providers-ansible_tower/commit/f24adea66fc17c3b4e8782336ba63cad555f05ca commit f24adea66fc17c3b4e8782336ba63cad555f05ca Author: Adam Grare <agrare> AuthorDate: Wed Apr 22 17:06:54 2020 +0000 Commit: Adam Grare <agrare> CommitDate: Wed Apr 22 17:06:54 2020 +0000 Merge pull request #218 from agrare/bz_1824846_catch_parser_errors_on_individual_job_templates Catch exceptions when parsing job_templates (cherry picked from commit 3b0cb7bef5920127f112762c7a5183d95295f72e) https://bugzilla.redhat.com/show_bug.cgi?id=1824846 app/models/manageiq/providers/ansible_tower/shared/inventory/parser/automation_manager.rb | 50 +- 1 file changed, 30 insertions(+), 20 deletions(-) Verified on 5.11.6 Reproducer 1)Add Tower to CFME 2)Make sure the Tower set up has a job template to which a variable with '\\' is being passed. 3)Wait for provider refresh to complete. On 5.11.6 (with the fix) , I have verified the following after the Tower provider was added: 1)UI shows provider refresh has completed 2)There are no errors in evm.log 3)I'm able to see all the objects under the provider. I also see the job template in question being listed in the UI. The job template shouldn't get listed in the UI since it's not usable. Clicking on the template doesn't take you to the template details page. I'll report a BZ to address this issue. I also see this warning logged in evm.log. This change was incorporated through https://bugzilla.redhat.com/show_bug.cgi?id=1824846 ----] W, [2020-06-03T12:27:42.321964 #1073065:2b0930dc05b4] WARN -- : MIQ(ManageIQ::Providers::AnsibleTower::Inventory::Parser::AutomationManager#configuration_scripts) Failed to parse job_template ID [7]: <unknown>): found unknown escape character while parsing a quoted scalar at line 2 column 10 *** Bug 1819310 has been marked as a duplicate of this bug. *** https://github.com/ManageIQ/manageiq/pull/20241 contains a change which actually fixes this case rather than just working around it. The newer version of ruby's yaml parser is able to handle this type of a payload. Recommend backporting that to resolve this issue in a better way. 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/RHSA-2020:2480 |