geni_sliver_info show the same time for creation and expiration

[lnevers@bbn.com]

The AM API acceptance test was run on March 11 08:06 am EDT. The AM API acceptance test verifies the sliver creation workflow by creating several slivers. Review of the manifests results for all createsliver operations showed that slivers had the same time for creation_time and expiration_time:

$ egrep ns4:geni_sliver_info acceptance.log |grep Nascent
        <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:56:38.166Z" expiration_time="2013-03-11T11:56:38.166Z" creation_time="2013-03-11T11:56:38.166Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>
        <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:58:50.284Z" expiration_time="2013-03-11T11:58:50.284Z" creation_time="2013-03-11T11:58:50.284Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>
        <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T07:59:15.198-04:00" expiration_time="2013-03-11T07:59:15.198-04:00" creation_time="2013-03-11T07:59:15.198-04:00" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>
        <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:59:40.323Z" expiration_time="2013-03-11T11:59:40.323Z" creation_time="2013-03-11T11:59:40.323Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>

The full log is available if more information is needed. Note, could not reproduce this problem.

[ibaldin@renci.org]

Can you elaborate on not being able to reproduce and also what the slice name was?

[lnevers@bbn.com]

Below are the 4 slices URNs for each of the geni_sliver_info in the initial ticket description:

Slice urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+acclne-115610" for the geni_sliver_info: <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:56:38.166Z" expiration_time="2013-03-11T11:56:38.166Z" creation_time="2013-03-11T11:56:38.166Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>

Slice urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+acclne-1157550" for the geni_sliver_info: <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:58:50.284Z" expiration_time="2013-03-11T11:58:50.284Z" creation_time="2013-03-11T11:58:50.284Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>

Slice urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+acclne-1157551" for the geni_sliver_info: <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T07:59:15.198-04:00" expiration_time="2013-03-11T07:59:15.198-04:00" creation_time="2013-03-11T07:59:15.198-04:00" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>

Slice urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+acclne-1157552" for the geni_sliver_info: <ns4:geni_sliver_info state="Nascent" start_time="2013-03-11T11:59:40.323Z" expiration_time="2013-03-11T11:59:40.323Z" creation_time="2013-03-11T11:59:40.323Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/>

Elaborating on not being able to reproduce: I re-ran the AM API acceptance tests and did not see the problem on subsequent runs. I also checked the sliver creation operations for several other slivers and did not see the problem. Could be a race condition.