Bug 725785

Summary: Unable to add 'RHEL6' tag to a test case
Product: [Other] TCMS Reporter: Petr Šplíchal <psplicha>
Component: ApplicationAssignee: Yuguang Wang <yuwang>
Status: CLOSED DUPLICATE QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 3.5CC: ctang, dli, junzhang, jzhao, mmalik, nli, ohudlick, vchen
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-28 10:21:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Šplíchal 2011-07-26 14:40:58 UTC
Description of problem:

I'm not able to tag test cases with the 'RHEL6' tag.

Version-Release number of selected component (if applicable):
Nitrate 3.5.0

Steps to Reproduce:
TestCase.add_tag(46490, 'RHEL6')

Actual results:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "nitrate.py", line 120, in request_with_cookies
    return self._parse_response(h.getfile(), sock)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1392, in _parse_response
    return u.close()
  File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close
    raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault 1: "MultipleObjectsReturned: get() returned more than one TestTag -- it returned 2! Lookup parameters were {'name': u'RHEL6'}">

Additional info:
Tagging with RHEL5 works fine.

Comment 1 Petr Šplíchal 2011-07-26 15:11:27 UTC
In the web UI it shows:

{"response": "Error when adding [u'RHEL6']", "rc": 1}

Comment 2 Yuguang Wang 2011-07-28 10:21:38 UTC

*** This bug has been marked as a duplicate of bug 725641 ***