Bug 1299862
Summary: | satellite-sync from base channel dump RHEL7 x86_64 2015-03-08 is failing with DataError: invalid byte sequence for encoding "UTF8": 0xc220 | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Jan Hutař <jhutar> |
Component: | Satellite Synchronization | Assignee: | Tomáš Kašpárek <tkasparek> |
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 570 | CC: | dyordano, jdobes, jiri.blaha, mgazdik, tlestach |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-13 13:27:03 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
Jan Hutař
2016-01-19 12:36:25 UTC
Yep, works on Sat570 with Oracle: [...] 09:40:12 Importing package metadata 09:40:12 Importing *relevant* package metadata: rhel-x86_64-hpc-node-7 (3705) ________________________________________ Importing: ######################################## - complete [...] When I have created RHEL7 dump on Satellite 5.7.0 @ embedded PostgreSQL, we were able to sync it into reproducer Satellite 5.6.0. Hi, tried to import "RHEL 7 (x86_64) + EUS + RHN Tools + Optional (Base 2015-11-22)" and "RHEL 7 (x86_64) + EUS + RHN Tools + Optional (Base 2015-03-08)" to Satellite 5.7.0@PostgreSQL with the same result: DataError('invalid byte sequence for encoding "UTF8": 0xc2 0x20\n',) invalid byte sequence for encoding "UTF8": 0xc2 0x20 This BZ looks to me like duplicate of Bug 1264467. Can anybody confirm that? Yes, it seem identical. Closing this bug, the second bug is already in MODIFIED state. *** This bug has been marked as a duplicate of bug 1264467 *** |