Description of problem: Fixes section of the Errata page is incorrectly formated. Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL5-re20090306.2-x86_64 How reproducible: all 3 advisories I have checked have that Steps to Reproduce: 1. Go to https://pipa02.englab.brq.redhat.com/rhn/errata/details/Details.do?eid=1325 2. Look at "Fixes" section Actual results: Fixes ["['CVE-2008-1372 bzip2: crash on malformed archive file']"] Expected results: Fixes CVE-2008-1372 bzip2: crash on malformed archive file
This is actually a problem in with the data in the DB. So could be a problem with hosted's exporter, our exporter or both... Spoke with pradeep about it, and re-assigning it to him.
Created attachment 336971 [details] tcpdump -i eth0 -nn -p 'tcp and host satellite.rhn.webqa.redhat.com' -w tcpdump.raw I have synced channels with '--no-errata', then started tcpdump and in other terminal re-synced from webqa, now without '--no-errata'. and for example here: https://pipa02.englab.brq.redhat.com/rhn/errata/details/Details.do?eid=1439 Fixes ['CVE-2007-2721 jasper crash in jpc_qcx_getcompparms'] ['CVE-2008-3520 jasper: multiple integer overflows in jas_alloc calls'] You may try yourself with admin/admin (it is Satellite-5.3.0-RHEL5-re20090323.0).
Created attachment 337475 [details] tcpdump -i eth0 -nn -p 'tcp and host satellite.rhn.webqa.redhat.com' -w tcpdump.raw What I have done to get the dump now: 1. # satellite-sync -c rhel-x86_64-as-4 --no-ssl --no-errata [...] Import complete: Begin time: Wed Apr 1 09:30:46 2009 End time: Wed Apr 1 10:47:36 2009 Elapsed: 1 hours, 16 minutes, 49 seconds 2. on the satellite check no. of the advisories => 1441 3. # tcpdump -i eth0 -nn -p 'tcp and host satellite.rhn.webqa.redhat.com' -w tcpdump.raw # this was started on the other console 4. # satellite-sync -c rhel-x86_64-as-4 --no-ssl [...] Import complete: Begin time: Wed Apr 1 11:09:16 2009 End time: Wed Apr 1 11:17:59 2009 Elapsed: 0 hours, 8 minutes, 43 seconds 5. Ctrl+C on tcpdump
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog. Please re-open if you disagree and wish further review. Cliff