NPE fetching a TestCase on cc-dev.oddsites.net

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: carljm, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
These platform URLs are both returning NPEs on cc-dev.oddsites.net:

http://cc-dev.oddsites.net:8080/tcm/services/v2/rest/testcases/1/?_type=json
http://cc-dev.oddsites.net:8080/tcm/services/v2/rest/testcases/1/latestversion/?_type=json

It's probably some kind of database corruption, tracking that down now. But only the platform ever interacts with this database, so whatever is corrupted, was corrupted by a platform API call. And this just showed up today, so whatever bug caused it is still there. Need to track down how it happened and fix it.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/20814675
Carl Meyer added a comment in Pivotal Tracker:   
   
Uploaded a database dump in case you have time to look at this, Vadim, since you're more familiar with the database schema and what might go wrong in it than I am.
Carl Meyer added a comment in Pivotal Tracker:   
   
Ok, it turned out this was a problem from something that has since been fixed - the two "sample" test cases that used to be part of the db creation scripts. They had product ID set as 1, and there was actually a product ID 1 in use in this database, so they were turning up as test case options for that product. But they had company ID 0, which didn't exist, which is what caused the NPE. So in this case I think just deleting those two rows is sufficient fix.
Carl Meyer changed story state to delivered in Pivotal Tracker
Carl Meyer changed story state to delivered in Pivotal Tracker
Carl Meyer changed story state to delivered in Pivotal Tracker
Carl Meyer added a comment in Pivotal Tracker:   
   
... and just fixed the same thing on cc.oddsites.net.
Cameron Dawson changed story state to accepted in Pivotal Tracker
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.