Bug 1075990

Summary: Satellite 5.6: CVE name changing syntax in 2014
Product: Red Hat Satellite 5 Reporter: Jan Dobes <jdobes>
Component: Satellite SynchronizationAssignee: Jan Dobes <jdobes>
Status: CLOSED ERRATA QA Contact: Pavel Studeník <pstudeni>
Severity: medium Docs Contact:
Priority: high    
Version: 560CC: cperry, pstudeni, vdanen, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-backend-2.0.3-27 spacewalk-java-2.0.2-64 satellite-schema-5.6.0.18-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1078330 1078850 1080985 1081189 (view as bug list) Environment:
Last Closed: 2014-04-23 12:16:19 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:
Bug Depends On:    
Bug Blocks: 924189, 1078330, 1078850, 1080985, 1081189    

Comment 5 Pavel Studeník 2014-04-11 12:59:03 UTC
Verified with 
* satellite-schema-5.6.0.18-1.el6sat.noarch
* spacewalk-java-2.0.2-63.el6sat.noarch
* spacewalk-backend-2.0.3-26.el6sat.noarch

Reproducer was:
0. package satellite-schema-5.6.0.16-1.el6sat.noarch
1. satellite-sync -c rhel-x86_64-server-6 --no-rpms --no-packages --no-kickstart
2. mkdir dump
3. rhn-satellite-exporter -c rhel-x86_64-server-6 --dir dump/
4. edit file vim dump/errata/0/rhn-erratum-100.xml.gz
5. satellite-sync -m dump/ -c rhel-x86_64-server-6 --force-all-errata

SYNC ERROR: unhandled exception occurred:

(Check logs/email for potentially more detail)

DataError('value too long for type character varying(13)\n',)
value too long for type character varying(13)

Comment 9 Pavel Studeník 2014-04-17 12:50:10 UTC
Verified with
 spacewalk-java-2.0.2-64.el6sat.noarch.rpm
 spacewalk-backend-2.0.3-27.el6sat.noarch.rpm
 satellite-schema-5.6.0.18-1.el6sat.noarch.rpm

Comment 11 errata-xmlrpc 2014-04-23 12:16:19 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0428.html