Bug 2177556

Summary: REX sometimes failed with "Incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string"
Product: Red Hat Satellite Reporter: matt jia <mjia>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.11.5CC: aruzicka
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:10:46 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:

Description matt jia 2023-03-12 23:22:27 UTC
Description of problem:

Applying erratas on some of the hosts failed with:

{""output"":""Runner error: Encoding::CompatibilityError - incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)""


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


How reproducible:

Hard

Steps to Reproduce:

Apply erratas with REX

Actual results:

Some of the hosts failed with:

{""output"":""Runner error: Encoding::CompatibilityError - incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)""


Expected results:

the job should finish successfully

Additional info:

The erratas had been installed on the hosts but it seems like Satellite does not like the data sent back from the hosts.

Comment 2 Adam Ruzicka 2023-03-13 08:58:00 UTC
Could we get logs from the smart proxy?

Comment 9 Eric Helms 2024-06-06 16:10:46 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.