Opened 12 years ago
Closed 12 years ago
#71 closed (fixed)
when slivers are defined, Resource.slices throws an exception
Reported by: | chaos@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 2012-09-04 client release |
Component: | Clients | Version: | |
Keywords: | v0.6.1 | Cc: | |
Dependencies: |
Description
This code:
... resource[datapath] = gmoc.Resource( resource_urn, type = 'datapath', pop = pop, operator = organization, ) print resource[datapath].slices ... <do a bunch of sliver and resource mapping stuff> ... print resource[datapath].slices
yields:
[] Traceback (most recent call last): File "./report_foam_relations", line 346, in <module> print resource[datapath].slices File "/home/chaos/gmoc.py", line 1157, in slices for mapName, sliver in self._slivers: TypeError: 'Sliver' object is not iterable
Change History (5)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Keywords: | v0.5.3 added; v0.5.0 removed |
---|
I think you caught one typo, but there's a deeper issue here. I still get:
Traceback (most recent call last): File "./report_foam_relations", line 354, in <module> print resource[datapath].slices File "/home/chaos/gmoc.py", line 1161, in slices for mapName, sliver in self.slivers: TypeError: 'Sliver' object is not iterable
I'm going to follow up via e-mail about the sliver/resource mapping problem in general. I am guessing that a code rewrite to come will make this bug OBE.
comment:3 Changed 12 years ago by
Keywords: | v0.6.1 added; v0.5.3 removed |
---|
Hmm... the sliver/resource mapping issue is fixed, but i still see this issue, which is a bug in resource.slices
. The code in the description still yields:
[] Traceback (most recent call last): File "./report_foam_relations", line 349, in <module> print resource[datapath].slices File "/home/chaos/gmoc.py", line 1175, in slices for mapName, sliver in self.slivers: TypeError: 'Sliver' object is not iterable
I'll poke a bit further and see if i can find the issue.
comment:4 Changed 12 years ago by
Yeah, so i think this is as simple as the syntax of Resource.slivers
having changed, and Resource.slices
not yet being updated to lookup slivers (in order to find their slices) the new way.
comment:5 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in 0.6.2! The code in the description now reports:
[] [<gmoc.Slice object at 0x8a9498c>, <gmoc.Slice object at 0x8a9490c>]
or, more informatively:
[] ['urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+chaos-poblano1101-datapath', 'urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+chaos-montreve-macaddr']
Closing.
My guess is that this is a side effect of some other sliver/resource mapping issue, but i wanted to go ahead and make a ticket for it so i don't forget to recheck it later.