Re-creating an expired sliver brings back expired resources

[lnevers@bbn.com]

The following is the sequence of events that lead to expired resources showing up in sliverstatus:

1. Created slice named 'lnexo'
2. Creates sliver 'lnexo' at GPO SM with an RSpec that requested 4 VMs.
3. Sliver and Slice 'lnexo' expired at "Tue Mar 12 11:40:00 UTC 2013"
4. Verified that sliver had expired and verified that resources were no longer available via SSH.
5. One hour later, (~ 12:21 UTC) re-created slice lnexo (see capture below)
6. Re-created sliver lnexo at GPO SM with the same RSpec as step 2, which reported "duplicate slice urn urn" (see capture below)
7. Checked the sliverstatus, which showed the "expired" resources from the previous test run. (see capture below)

$ omni.py createslice lnexo                                 
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Created slice with Name lnexo, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo, Expiration 2013-03-13 13:20:58+00:00
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createslice:

  Options as run:
		framework: pg

  Args: createslice lnexo

  Result Summary: Created slice with Name lnexo, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo, Expiration 2013-03-13 13:20:58+00:00
 
INFO:omni: ============================================================

lnevers@arendia:~/gcf-2.2/exorspec$ omni.py createsliver -a eg-gpo lnexo EG-CT-1-gpo.rspec 
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo expires on 2013-03-13 13:20:58 UTC
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Creating sliver(s) from rspec file EG-CT-1-gpo.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo
WARNING:omni:Failed CreateSliver for slice lnexo at https://bbn-hn.exogeni.net:11443/orca/xmlrpc.  Error from Aggregate: code 2: ERROR: duplicate slice urn urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo.
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:

  Options as run:
		aggregate: ['eg-gpo']
		framework: pg

  Args: createsliver lnexo GPO/EG-CT-1-gpo.rspec

  Result Summary: Failed CreateSliver for slice lnexo at https://bbn-hn.exogeni.net:11443/orca/xmlrpc.  Error from Aggregate: code 2: ERROR: duplicate slice urn urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo. 
INFO:omni: ============================================================

lnevers@arendia:~/gcf-2.2/exorspec$ omni.py sliverstatus -a eg-gpo lnexo  
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo expires on 2013-03-13 13:20:58 UTC
INFO:omni:Substituting AM nickname eg-gpo with URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo:
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: ready
INFO:omni:Sliver status for Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo at AM URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc
INFO:omni:{
  "geni_status": "ready", 
  "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo", 
  "geni_resources": [
    {
      "orca_expires": "Tue Mar 12 11:40:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+bd21a52d-af3b-4506-ba5b-16d97b44dd43#center", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Tue Mar 12 11:40:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+bd21a52d-af3b-4506-ba5b-16d97b44dd43#geni2", 
      "geni_error": "", 
      "geni_status": "Active"
    }, 
    {
      "orca_expires": "Tue Mar 12 11:40:00 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+bd21a52d-af3b-4506-ba5b-16d97b44dd43#geni1", 
      "geni_error": "", 
      "geni_status": "Active"
    }
  ]
}
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed sliverstatus:

  Options as run:
		aggregate: ['eg-gpo']
		framework: pg

  Args: sliverstatus lnexo GPO/EG-CT-1-gpo.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo expires on 2013-03-13 13:20:58 UTC
Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexo at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: ready.
 Returned status of slivers on 1 of 1 possible aggregates. 
INFO:omni: ============================================================
lnevers@arendia:~/gcf-2.2/exorspec$ date
Tue Mar 12 08:27:51 EDT 2013
lnevers@arendia:~/gcf-2.2/exorspec$ 

[ibaldin@renci.org]

No new slivers were created. Once the system reports 'duplicate urn' no further action is taken, so what you are looking at is the snapshot of the previous slice under the same urn. We need to check why it is reporting old slivers as active.

[anirban@renci.org]

Garbage collection happens after about 40 minutes of expiry. So, it is possible to use the same slice urn after that time interval. We have not been able to replicate the reporting of "Active" status for expired slivers. In our testings at the bbn and renci racks, sliverstatus returns "Closed" status for expired slivers.

[ibaldin@renci.org]

Slice GC is lazy, so no real timing guarantees can be placed on it.

It should be possible to force GC by deleting the slice explicitly, at which time the slice name becomes reusable again.

[ahelsing@bbn.com]

In this case of course the user cannot do the delete, as the slice itself has expired.

Can't the GC be triggered by the request to act on the local sliver(s)? That is, when the user calls 'createsliver', notice that there is an existing entry under the same name that has since expired, do the GC, and then process the 'createsliver' call?