Red Hat Bugzilla – Bug 477703
Exported content need to conform to Satellite schema (e.g., errata description not exceeding 4k chars)
Last modified: 2010-10-23 02:43:34 EDT
Per discussion with Prad, cloning this for Satellite for exporter side, to port from Hosted fix when there is one.
+++ This bug was initially created as a clone of Bug #477701 +++
Description of problem:
In the case of different character encodings, content exported from Hosted may exceed Satellite schema, causing satellite-sync failure.
Recently due to special characters in Errata Description of erratum https://rhn.redhat.com/rhn/errata/details/Details.do?eid=7924, the exported content exceeded 4000 char limit causing all (pre-5.2) Satellite-syncs to fail for RHEL 5 channels.
Bug 476751 - ValueError: string data too large
Bug 476756 - sat-sync unhandled exception 1461, 'ORA-01461: can bind a LONG
value only for insert into a LONG columnn'
The short term fix was to reduce char count for the description of the erratum in question even further. For the long-term fix on the export side, need to make sure the exported content conforms to the schema on import side (errata description is one specific field, this needs to be done in general).
Version-Release number of selected component (if applicable):
See example above.
Steps to Reproduce:
1. See example above.
See example above.
Regardless of character encoding, the exported content from Hosted should conform to schema on importer side (Satellite).
*** Bug 476756 has been marked as a duplicate of this bug. ***
May I get test reproduction steps for this please?
synced satellite that had errata RHSA-2008:1017 in the channels and the sync passed.
Sync of a 5.0.2 Satelite failed with "ValueError: string data too large" today.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.