Opened 11 years ago

Last modified 8 years ago

#1169 new task

IZ228: Restart of components should be tested

Reported by: crei Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: Sun hedeby
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=228]

        Issue #:      228             Platform:     Sun           Reporter: crei (crei)
       Component:     testsuite          OS:        All
     Subcomponent:    hedeby          Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    TASK
                                  Target milestone: milestone 1
      Assigned to:    crei (crei)
      QA Contact:     crei
          URL:
       * Summary:     Restart of components should be tested
   Status whiteboard:
      Attachments:

     Issue 228 blocks:
   Votes for issue 228:     Vote for this issue


   Opened: Wed Aug 6 05:21:00 -0700 2008 
------------------------


Restart of components should be tested

------- Additional comments from marcingoldyn Thu Feb 7 07:13:14 -0700 2008 -------

reassign

------- Additional comments from marcingoldyn Thu Feb 7 07:14:44 -0700 2008 -------

I will do some stress test for starting and stoping components

First we will test the jvms there will be couple of start and stops than
components couple of starts and stops.

------- Additional comments from rhierlmeier Wed Feb 27 08:44:58 -0700 2008 -------

Seperate tests for all components

exceutor/restart
     - execute a long running script
     - java test program submits the jobs
     - restart executor
     - the test script must be killed
     - java test program must receive GrmRemoteException
       (may be ExecutionException)
     - check the events from the history

rp/restart
     - run "sdmadm sr" and store result (r1)
     - run "sdmadm sr -cached" and store the result (r2)
     - compare r1 to r2
     - restart rp
     - run "sdmadm sr" and store (r3)
     - run "sdmadm sr -cached" and store (r4)
     - compare all results
     - check the events from the history

ge_adapter/restart
     - run "sdmadm sr"
     - restart ge_adapter
     - compare that all resources still available
     - check the events from the history

ca/restart
     - restart ca
     - get certificate of a user from ca
     - check the events from the history

cs/restart
     - test it with restarting the cs jvm
     - test that all components can context CS
     - check the events from the history

reporter/restart

     - delete reporter file
     - restart reporter
     - check events
     - restart each service
     - check service events

------- Additional comments from rhierlmeier Wed Feb 27 09:33:51 -0700 2008 -------

Additional test for spare_pool:

   - stop spare_pool
   - remove resources from spool directory
   - start spare_ppl
   - check RESOURCE REMOVED events and document it

------- Additional comments from rhierlmeier Wed Feb 27 09:46:09 -0700 2008 -------

*** Issue 235 has been marked as a duplicate of this issue. ***

------- Additional comments from marcingoldyn Wed May 21 08:20:23 -0700 2008 -------

ca jvm ge_adapter are done

------- Additional comments from marcingoldyn Thu May 29 06:33:11 -0700 2008 -------

additional test

start all components/stop all components

------- Additional comments from marcingoldyn Wed Aug 6 03:02:39 -0700 2008 -------

we should complete this task

Change History (0)

Note: See TracTickets for help on using tickets.