Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description of problem: I am getting "<ProtocolError for tcms.engineering.redhat.com/xmlrpc/: 500 INTERNAL SERVER ERROR>" after creating new testcase and running "tcms-submit --link=all --coverage" command. Version-Release number of selected component (if applicable): qa-tools-3.1-2.x86_64 and qa-tools-3.1-3.x86_64 How reproducible: *for new test case in "/tests/redhat-access-insights/Regression/bz1323187-registering-without-authentication-leads-to-bogus" *for other component test I dont know yet. *"tcms-submit --update" for other testcases seems working Steps to Reproduce: 0. cd ~/tests/redhat-access-insights/ 1.git status 2. git add Regression/bz1323187-registering-without-authentication-leads-to-bogus/* 3. git commit -m "Regression/bz1323187-registering-without-authentication-leads-to-bogus/ - comment repair" 4. git push 5. cd Regression/bz1323187-registering-without-authentication-leads-to-bogus/ 6. make tag && git push --tags && make bkradd 7. tcms-submit --link=all --coverage Actual results: jhouska@dhcp-24-130 bz1323187-registering-without-authentication-leads-to-bogus]$ tcms-submit --link=all --coverage Bugs in Makefile/Beaker: 1323187 Searching for existing Test Case(s) Found test case TC#0544328 - /CoreOS/redhat-access-insights/Regression/bz1323187-registering-without-authentication-leads-to-bogus Searching bugs with linked TC#544328 Found bug(s): None WARNING Failed to find component redhat-access-insights, please add it to TCMS manually Git link: http://pkgs.devel.redhat.com/cgit/tests/redhat-access-insights/tree/Regression/bz1323187-registering-without-authentication-leads-to-bogus Relevancy set: distro = rhel-4, rhel-5: False Description set in Structured Field ERROR Failed to send TC#0544328 to the server: <ProtocolError for tcms.engineering.redhat.com/xmlrpc/: 500 INTERNAL SERVER ERROR> Expected results: Not an error. Additional info: After mannualy adding 544328 test case into 21477 plan and 298712 run all seems working well.