Custom Query (138 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 138)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#158 fixed Check expires in request rspec and fail createsliver as appropriate somebody lnevers@bbn.com
Description

Created a 2 VM sliver at the GPO SM with 2 VMs and 1 lan (attaching RSpec) and the sliver failed as follows:

$ omni.py sliverstatus -a eg-gpo lnexp ./exo-2vm-1lan-bbn.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+lnexp expires on 2013-03-26 00:00:00 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+lnexp:
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: failed
INFO:omni:Sliver status for Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc
INFO:omni:{
  "geni_status": "failed", 
  "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp", 
  "geni_resources": [
    {
      "orca_expires": "Tue Mar 12 16:07:42 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+f2f8a638-2547-4882-a043-8cb7e21b5c7f#geni1", 
      "geni_error": "Reservation 0bc447cb-890e-4e8a-890c-5dcc09bad1bb (Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp) is in state 
[Failed,None], err=unexpected ticket failure, message=negative duration for term, 
stack=Exception stack trace: \norca.shirako.time.Term.validate(Term.java:773)
\norca.shirako.kernel.ReservationClient.validateOutgoing(ReservationClient.java:2288)
\norca.shirako.kernel.KernelWrapper.ticket(KernelWrapper.java:874)
\norca.shirako.core.ServiceManager.bid(ServiceManager.java:142)
\norca.shirako.core.ServiceManager.tickHandler(ServiceManager.java:469)
\norca.shirako.core.Actor.actorTick(Actor.java:431)\norca.shirako.core.Actor.access$000(Actor.java:51)
\norca.shirako.core.Actor$1.process(Actor.java:341)\norca.shirako.core.Actor.actorMain(Actor.java:384)
\norca.shirako.core.Actor$4.run(Actor.java:944)\njava.lang.Thread.run(Thread.java:662)\n\n", 
      "geni_status": "Failed"
    }, 
    {
      "orca_expires": "Tue Mar 12 16:07:42 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+f2f8a638-2547-4882-a043-8cb7e21b5c7f#center", 
      "geni_error": "Reservation 12346895-8f39-424a-a163-6f188dc2b4a3 (Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp) is in state 
[Failed,None], err=unexpected ticket failure, message=negative duration for term, stack=Exception stack trace: 
\norca.shirako.time.Term.validate(Term.java:773)
\norca.shirako.kernel.ReservationClient.validateOutgoing(ReservationClient.java:2288)
\norca.shirako.kernel.KernelWrapper.ticket(KernelWrapper.java:874)
\norca.shirako.core.ServiceManager.bid(ServiceManager.java:142)
\norca.shirako.core.ServiceManager.tickHandler(ServiceManager.java:469)
\norca.shirako.core.Actor.actorTick(Actor.java:431)\norca.shirako.core.Actor.access$000(Actor.java:51)
\norca.shirako.core.Actor$1.process(Actor.java:341)\norca.shirako.core.Actor.actorMain(Actor.java:384)
\norca.shirako.core.Actor$4.run(Actor.java:944)\njava.lang.Thread.run(Thread.java:662)\n\n", 
      "geni_status": "Failed"
    }, 
    {
      "orca_expires": "Tue Mar 12 16:07:42 UTC 2013", 
      "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+f2f8a638-2547-4882-a043-8cb7e21b5c7f#geni2", 
      "geni_error": "Reservation 7cf2a6be-cb2c-423b-8b4a-6bc54fd6246d (Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp) is
 in state [Failed,None], err=unexpected ticket failure, message=negative duration for term, stack=Exception stack trace: 
\norca.shirako.time.Term.validate(Term.java:773) \norca.shirako.kernel.ReservationClient.validateOutgoing(ReservationClient.java:2288)
\norca.shirako.kernel.KernelWrapper.ticket(KernelWrapper.java:874)\norca.shirako.core.ServiceManager.bid(ServiceManager.java:142)
\norca.shirako.core.ServiceManager.tickHandler(ServiceManager.java:469)\norca.shirako.core.Actor.actorTick(Actor.java:431)
\norca.shirako.core.Actor.access$000(Actor.java:51)\norca.shirako.core.Actor$1.process(Actor.java:341)
\norca.shirako.core.Actor.actorMain(Actor.java:384)\norca.shirako.core.Actor$4.run(Actor.java:944)
\njava.lang.Thread.run(Thread.java:662)\n\n", 
      "geni_status": "Failed"
    }
  ]
}
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed sliverstatus:

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

  Args: sliverstatus lnexp ./exo-2vm-1lan-bbn.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp expires on 2013-03-26 00:00:00 UTC
Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnexp at AM https://bbn-hn.exogeni.net:11443/orca/xmlrpc has overall SliverStatus: failed.
 Returned status of slivers on 1 of 1 possible aggregates. 
INFO:omni: ============================================================
#22 fixed clarify minor inconsistencies in rack layout diagram jonmills@renci.org chaos@bbn.com
Description

In using the rack layout diagram at https://wiki.exogeni.net/doku.php?id=public:hardware:rack_layout, to label our rack, I found a few minor inconsistencies:

  • Our iSCSI is mounted at U25-U26, where the diagram shows U24-U25. Is this an error in the diagram or an error in our rack? If the latter, should it be fixed, or just noted as a footnote on the rack diagram or elsewhere?
  • The SSG5 is not shown in that diagram. It's not rackmounted, but it is a networked device in the rack, so i think it would be good to note it so people can tell from the diagram what it is.
  • No hostnames are given in the layout page for the iSCSI array, the SSG5, or the console. Of those, i think the iSCSI array and the SSG5 actually have hostnames (since they are networked), so we should agree on what they are.

These are minor, but please get back to me on them so i can close out EG-ADM-1 step 4A.

#192 fixed Clean up old DPIDs jbs@bbn.com jbs@bbn.com
Description

FOAM caches the DPIDs that it sees, so that it can let you reserve resources on them even if the switch is down at the time of the reservation. If a DPID changes, the old one stays cached in FOAM. This happened on the ExoGENI racks; clean up the old DPIDs in FOAM.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.