Bug 713662 - [Extremely Urgent] Some test plans lost all|most|some test cases this afternoon.
Summary: [Extremely Urgent] Some test plans lost all|most|some test cases this afternoon.
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.4.1
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 06:58 UTC by Kenichi Takemura
Modified: 2023-10-20 16:24 UTC (History)
10 users (show)

Fixed In Version: 3.5.0-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 815929 0 urgent VERIFIED Expanding a testcase shows test procedure values as None. 2023-10-20 16:24:49 UTC

Internal Links: 815929

Description Kenichi Takemura 2011-06-16 06:58:20 UTC
Description of problem:

All or most of or some of test cases in my test plans are lost this afternoon.
I was running a test run from the plan 3937 and the next thing I knew is all test case are empty.

https://tcms.engineering.redhat.com/plan/3984/
https://tcms.engineering.redhat.com/plan/3937/

Need a quick action such as recover since this issues stops our testing work completely.

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

How reproducible:
Happened this afternoon. Problem still exists.

Steps to Reproduce:
1. Not sure.
2.
3.
  
Actual results:
Test plans lost test cases.
I have no idea this happened with my plans or other users are also affected.

Expected results:
Should not happen again.

Additional info:

Comment 1 Kenichi Takemura 2011-06-16 07:57:23 UTC
I recovered test cases in the plan 3937 because we need to finish testing as soon as possible.

https://tcms.engineering.redhat.com/plan/3937/

So please check 3984 it still has no data.

What I did 

- Removed test cases from the plan
- Removed some test runs
- Import test cases from XML-RPC again

Comment 2 Chaobin Tang 2011-06-16 13:19:00 UTC
Please re-check now.

We have done a urgent data recovery today.

We are still working on the root cause. Will update this later.

Comment 3 Len DiMaggio 2011-06-23 15:09:44 UTC
Other test cases were lost also:

Actions, Setuop and Expected Results for this test case for example and you will see that it doesn't contain anything:
Case: 94783

<vchen> ldimaggi_brb, yes, we've find that SQL in DB log, still probing the root cause
<ldimaggi_brb> vchen, thanks!
<vchen> ldimaggi_brb, will try to recover the cases from DB log.

Comment 4 Jin Zhao 2011-07-14 05:27:37 UTC
After db recovery, can not reproduce this issue until now. 
So change the status VERIFY on version 3.5.0-1

Comment 5 Jin Zhao 2012-06-26 03:54:11 UTC
Reproduce on Jun 26 morning CST

Comment 6 Satyabrata Maitra 2012-07-03 10:08:27 UTC
https://tcms.engineering.redhat.com/run/41797/?from_plan=5366
https://tcms.engineering.redhat.com/run/41798/?from_plan=5366

These test runs also having empty data, apart from the test comments.

Comment 7 yawei Li 2012-07-05 04:02:31 UTC
(In reply to comment #6)
> https://tcms.engineering.redhat.com/run/41797/?from_plan=5366
> https://tcms.engineering.redhat.com/run/41798/?from_plan=5366
> 
> These test runs also having empty data, apart from the test comments.

The root cause is that these two test runs were created against on the empty content test case during the accident. They are updated now.

Comment 8 Xin Gao 2012-07-16 09:59:00 UTC
Verify 3.7.0-4 on stage -->PASS

Verify steps:
1. Create plan.
    a. Create a new plan1: click PlANNING -> New Plan.
    b. Create a new plan2: click PlANNING -> New Plan.
2. Create case.
    a. In new plan1, create three new cases, newcase1, newcase2, newcase3.
    Note: must write sth to "Setup", "Break down", "Actions", "Expected Results".
    b. In new plan2, create two new cases, newcase4, newcase5.
    Note: must write sth to "Setup", "Break down", "Actions", "Expected Results".
3. Edit case.
    a. Enter into editing page of newcase1, and edit the fields of "Setup", "Break down", "Actions", "Expected Results". Then Click Save.
    b. Enter into editing page of newcase2, and edit the fields of "Setup", "Break down", "Actions", "Expected Results". Then Click Save.
    c. Enter into editing page of newcase3, and edit the fields of "Setup", "Break down", "Actions", "Expected Results". Then Click Save.
    d. Enter into editing page of newcase4, and edit the fields of "Setup", "Break down", "Actions", "Expected Results". Then Click Save.
    e. Enter into editing page of newcase5, and edit the fields of "Setup", "Break down", "Actions", "Expected Results". Then Click Save.
4. Do step 3 again.
5. Delete one case.
    a. Click ADMIN -> Test cases.
    b. Click Test cases.
    c. find "newcase1"(that is created in step 2) via search field.
    d. Click "newcase1". 
    e. Click Delete.  Then click "Yes, I'm sure".
6. Check other newcases.
   Note: check every newcases' "Setup", "Break down", "Actions", "Expected Results".

Actual result:
After step 6, all others newcases' "Setup", "Break down", "Actions", "Expected Results" were not be deleted.


Note You need to log in before you can comment on or make changes to this bug.