Opened 12 years ago

Closed 12 years ago

#16 closed (fixed)

Resource available is not in synch with information in listresources

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone: IG-EXP-1
Component: Experiment Version: SPIRAL4
Keywords: Cc:
Dependencies:

Description

There are instances of resource information out of synch between listresources and reserved resources. Occurred 05/15 9:00 eastern.

According to listresources "pc5" is available, but Chaos checked the reservations on the rack and found pc5 was in a slice I reserved called pgeni-gpolab-bbn-com+slice+image which failed due to lack of resources yesterday afternoon.

Change History (5)

comment:1 Changed 12 years ago by lnevers@bbn.com

Also checked sliverstatus to verify the non-existance of the sliver, which reported:

ERROR:omni:Cannot get sliver status for 
urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+image: Could not get slice credential:
Exception: PG Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+image does not exist.

comment:2 Changed 12 years ago by lnevers@bbn.com

On 5/15/12 9:47 AM, Leigh Stoller wrote:

I just ran discover and it pc5 is not available. Are you looking for the available tag. See ticket about this a couple of weeks ago.

The ticket is stating that node pc5 is listed as available in listresources, but when Chaos checked, she found it was reserved for an experiment that failed yesterday.

comment:3 Changed 12 years ago by lnevers@bbn.com

Also, after two failed attempt to create 2VM experiment, there seems to be only one pcvm available.

Some questions:

  1. What is the current allocation/reservation state for the pcvm in the rack now?
  1. If all pcvms are available, how many can I get at once?

comment:4 Changed 12 years ago by lnevers@bbn.com

Hi. I just ran discover and the output shows this for pc5:

<available now="false" />

Lbs

Sorry, the original intent of this ticket was to capture the fact that pc5 seems to be reserved for a sliver creation which failed.

The list resources is right, the mismatch is for the resource request failed.

comment:5 Changed 12 years ago by lnevers@bbn.com

Resolution: fixed
Status: newclosed

This is no longer an issue, closing ticket.

Note: See TracTickets for help on using tickets.