RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2020426 - rhc throws serialization error after executing remediations playbook
Summary: rhc throws serialization error after executing remediations playbook
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhc-worker-playbook
Version: 8.5
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 8.6
Assignee: Link Dupont
QA Contact: Pavol Kotvan
URL:
Whiteboard:
Depends On:
Blocks: 2056862 2057720
TreeView+ depends on / blocked
 
Reported: 2021-11-04 20:04 UTC by Christian Marineau
Modified: 2022-11-29 14:24 UTC (History)
7 users (show)

Fixed In Version: rhc-worker-playbook-0.1.8-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2056862 2057720 (view as bug list)
Environment:
Last Closed: 2022-05-10 14:27:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:
cmarinea: needinfo-
pm-rhel: mirror+


Attachments (Terms of Use)
rhcd log (111.95 KB, text/plain)
2021-11-19 03:32 UTC, Kazuo Moriwaka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ESSNTL-1370 0 None None None 2021-11-04 20:04:43 UTC
Red Hat Issue Tracker RHELPLAN-101790 0 None None None 2021-11-05 04:48:21 UTC
Red Hat Issue Tracker RHELPLAN-101791 0 None None None 2021-11-05 04:48:22 UTC
Red Hat Product Errata RHBA-2022:1953 0 None None None 2022-05-10 14:27:57 UTC

Description Christian Marineau 2021-11-04 20:04:19 UTC
Description of problem:

Each time a remediations playbook is executed via RHC, the following log entry is observed:

[rhcd] 2021/10/01 16:49:37 /builddir/build/BUILD/rhc-0.2.0/cmd/yggd/grpc.go:168: cannot send message 0e8eb387-acf2-48f9-8975-e6165f0fb2b3: rpc error: code = Internal desc = Failed to serialize response!


Expected results:
No error message

Comment 1 Link Dupont 2021-11-05 13:22:45 UTC
What version of insights-client and rhc-worker-playbook is installed when this occurs?

Can you attach a full log dump with log-level = "trace"? (journalctl -u rhcd > rhcd.log)

Comment 2 Kazuo Moriwaka 2021-11-19 03:32:10 UTC
Created attachment 1842652 [details]
rhcd log

Comment 3 Kazuo Moriwaka 2021-11-19 03:35:56 UTC
I hit same issue.
I attached rhcd's log with log-level = "trace"

Packages:
insights-client-3.1.7-1.el8_5.noarch
rhc-0.2.0-3.el8.x86_64
rhc-worker-playbook-0.1.5-3.el8_4.x86_64

Comment 12 errata-xmlrpc 2022-05-10 14:27:51 UTC
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 (rhc-worker-playbook bug fix and enhancement update), 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-2022:1953


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