Opened 9 years ago

Last modified 9 years ago

#160 new

sliverstatus prevents deletesliver for sliver which has failed at createsliver time

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone:
Component: Experiment Version: SPIRAL5
Keywords: sliver status Cc:
Dependencies:

Description

According to Ilia:

When a slivercreation fails there is garbage collection that must occur before the sliver name can be re-used. An experimenter can deletesliver to force the cleanup and thus be able to re-use the sliver name again.

Two scenarios have been tested which found conflicting results:

Scenario1:

  1. create slice - OK
  2. create sliver w/bad rspec, which causes expected failure - OK
  3. delete sliver - OK
  4. re-create the same sliver again with corrected rspec - OK

Scenario2:

  1. create slice - OK
  2. create sliver w/bad rspec, which causes expected failure - OK
  1. sliverstatus reports "Other Exception: java.lang.NullPointerException?" - Maybe ok?
  2. Delete sliver fails with "(got result 'False'). (no reason given) " - Can no longer delete the sliver

Change History (1)

comment:1 Changed 9 years ago by ahelsing@bbn.com

See related ticket #156

Note: See TracTickets for help on using tickets.