Opened 8 years ago

Last modified 8 years ago

#1457 new

AL2S aggregate does not return updated expiration date for listresources command

Reported by: Owned by:
Priority: major Milestone:
Component: STITCHING Version: SPIRAL7
Keywords: GENI Network Stitching Cc:


When a sliver is renewed at the al2s aggregate the change is applied and all commands show the new date (ex. sliverstatus).

There is one exception, the listresources command returns the original date and not the updated expiration date. Here is an example that show how the command show different expiration dates for a slice:

The sliverstatus output show the renew date "2015-05-30"

$ stitcher sliverstatus triangle -a al2s
10:46:04 INFO    : {
  "geni_status": "ready", 
  "geni_urn": "", 
  "foam_pend_reason": [], 
  "foam_expires": "2015-05-30 00:00:00+00:00", 
  "geni_resources": [
      "geni_urn": "", 
      "geni_error": "", 
      "geni_status": "ready"
  "foam_status": "approved"
Slice expires on 2015-05-30 00:00:00 UTC
Slice triangle at AM al2s has overall SliverStatus: ready.

While the listresources on same sliver shows the expiration date of "2015-03-11":

$ stitcher listresources triangle -a al2s
10:47:34 INFO    : Reservation at al2s in slice triangle expires at 2015-03-11 18:08:33 (UTC).
Queried resources for slice triangle from 1 of 1 aggregate(s).
Reservation at al2s in slice triangle expires at 2015-03-11 18:08:33 (UTC).

Note that 2015-03-11 was the initial expiration date for the sliver, the sliver has been renewed twice and neither of those expiration dates show.

This is only a problem with the AL2S FOAM aggregate.

Change History (1)

comment:1 Changed 8 years ago by Aaron Helsinger

Sent Luke patched source that indicates where & how to get the correct date in the manifest, but didn't make that change

Note: See TracTickets for help on using tickets.