Bug 1500185

Summary: [5.7] - same errata synced into two organizations break multiple errata queries
Product: Red Hat Satellite 5 Reporter: Tomáš Kašpárek <tkasparek>
Component: ServerAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED ERRATA QA Contact: Pavel Studeník <pstudeni>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 570CC: jdobes, ktordeur, mdekan, pstudeni, rdrazny, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-2.3.8-163-sat Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1486190 Environment:
Last Closed: 2017-10-31 12:25:12 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: 1486190    
Bug Blocks:    

Comment 4 Pavel Studeník 2017-10-18 13:52:49 UTC
# rpm -q spacewalk-java
spacewalk-java-2.3.8-160.el6sat.noarch

Reproducer:
 >> spacewalk-repo-sync -c channel1 -u https://dl.fedoraproject.org/pub/epel/7/x86_64/ -i  python34-lammps*
 >> spacewalk-repo-sync -c channel2 -u https://dl.fedoraproject.org/pub/epel/7/x86_64/ -i  python34-lammps*
 >> spacecmd clear_caches
 >> spacecmd  errata_details  FEDORA-EPEL-2017-628075ea93
INFO: Connected to https://localhost/rpc/api as admin
...

  File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close
    raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault -1: 'redstone.xmlrpc.XmlRpcFault: unhandled internal exception: query did not return a unique result: 2'>

Verified with spacewalk-java-2.3.8-164.el6sat.noarch.rpm

>> spacecmd  errata_details  FEDORA-EPEL-2017-628075ea93
INFO: Connected to https://localhost/rpc/api as admin
Name:       FEDORA-EPEL-2017-628075ea93
Product:    Fedora EPEL 7
Type:       Product Enhancement Advisory
Issue Date: 9/4/17

Comment 6 errata-xmlrpc 2017-10-31 12:25:12 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.

https://access.redhat.com/errata/RHBA-2017:3085