Opened 10 years ago

Closed 10 years ago

#5 closed (fixed)

create sliver generates "assign: Invalid Assign Output" error

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone:
Component: AM Version: SPIRAL4
Keywords: Cc:
Dependencies:

Description

Using an rspec with the following topology:

  • 3 nodes on lan1
  • 3 nodes on lan2
  • 1 node from lan1 connected via lan3 to 1 node on lan2.

The create sliver fails with the same error on both InstaGENI Utah and PG Utah:

Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+insta2node expires within 1 day(s) on 2012-05-02 01:09:36 UTC
Asked https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 to reserve resources. No manifest Rspec returned. 
*** ERROR: assign: Invalid Assign Output (expected "precheck:" line).*** ERROR: mapper: Unretriable error. Giving up.
seed = 1335902156
Physical Graph: 4
Calculating shortest paths on switch fabric.
TOP:9: Auto-assigning bandwidth on trivial or emulated links not allowed!
TOP:10: Auto-assigning bandwidth on trivial or emulated links not allowed!
TOP:11: Auto-assigning bandwidth on trivial or emulated links not allowed!
TOP:12: Auto-assigning bandwidth on trivial or emulated links not allowed!
TOP:13: Auto-assigning bandwidth on trivial or emulated links not allowed!
TOP:14: Auto-assigning bandwidth on trivial or emulated links not allowed!
ASSIGN FAILED:
*** ERROR: assign: Invalid Assign Output (expected "precheck:" line).

Attaching RSpec insta-3vm-3lan-c.rspec used in createsliver.

Attachments (1)

insta-3vm-3lan-c.rspec (3.8 KB) - added by lnevers@bbn.com 10 years ago.

Download all attachments as: .zip

Change History (4)

Changed 10 years ago by lnevers@bbn.com

Attachment: insta-3vm-3lan-c.rspec added

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

On 5/1/12 4:02 PM, Leigh Stoller wrote:

> One more time ...
>
>> �- 3 nodes on lan1
>> �- 3 nodes on lan2
>> �- 1 node from lan1 connected via lan3 to 1 node on lan2.
>>
>> �The create sliver fails with the same error on both InstaGENI Utah and PG
>> �Utah:
> So, your rspec includes this:
>
>   <property source_id="VM-2:if0" dest_id="VM-4:if0" capacity="0"
>    <property source_id="VM-4:if0" dest_id="VM-2:if0" capacity="0"
>    <property source_id="VM-2:if0" dest_id="VM-3:if0" capacity="0"
>    <property source_id="VM-4:if0" dest_id="VM-3:if0" capacity="0"
>    <property source_id="VM-3:if0" dest_id="VM-2:if0" capacity="0"
>    <property source_id="VM-3:if0" dest_id="VM-4:if0" capacity="0"
>
> With the fix I put in yesterday, this is confusing things.
> Best to take these back out. :-)

These capacity value are generated by Flack. Please note that I did not specify any capacity values. The RSpec that was generated had a capacity="100000" for lan3, while lan1 and lan2 defaulted to capacity="0".

Just to be sure I understand your comment, what do you mean by "Best to take these back out"? Do you want me to remove the values from the RSpec? or do you mean take out the software changes?

If the capacity=0 values should be removed from the RSpec, than the flack defaults should also change?!?

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

On 5/1/12 4:22 PM, Jonathon Duerig wrote: I just talked this over with Matt and he is fixing it.

Will verify and update ticket, when fix is available.

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

Resolution: fixed
Status: newclosed

Problem no longer occurs, closing ticket.

Note: See TracTickets for help on using tickets.