Custom Query (98 matches)
Results (1 - 3 of 98)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2 | fixed | Unable to use OpenVZ resources in slivers | ||
Description |
Using version ??? on 04/25/2012, sent email to instageni-ops@flux.utah.edu: Created a sliver with 2 OpenVZ hosts, the sliver was created successfully, but the sliverstatus shows that the 'pg_status' is 'not ready'. Attempts to login to the 2 nodes fail with a timeout. Connections were attempted over 40 minutes after sliver creation. This problem is reproducible Response to the email: On 4/25/12 11:15 PM, Robert Ricci wrote:
|
|||
#3 | fixed | listresources state mismatch for available nodes | ||
Description |
Based on the listresources, the aggregate shows all nodes as available, but creating a sliver with two node of sliver_type "raw-pc" results in a failure that stated the the nodes requested are not available. The full listresources output will be attached to the ticket, and the sliver creation error is shown here: lnevers@sendaria:~/gcf-1.6.1$ ./src/omni.py -a insta-utah createsliver lnrawv2 instageni-v2.rspec --api-version 2 INFO:omni:Loading config file omni_config INFO:omni:Using control framework pgeni INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnrawv2 expires within 1 day on 2012-04-27 23:51:54 UTC INFO:omni:Substituting AM nickname insta-utah with URL https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0, URN unspecified_AM_URN INFO:omni:Substituting AM nickname insta-utah with URL https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0, URN unspecified_AM_URN INFO:omni:Creating sliver(s) from rspec file instageni-v2.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnrawv2 INFO:omni:Asked https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 to reserve resources. Result: INFO:omni:<!-- Reserved resources for: Slice: lnrawv2 At AM: URL: https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 --> INFO:omni: ------------------------------------------------------------ INFO:omni: Completed createsliver: Options as run: aggregate: insta-utah api_version: 2 framework: pgeni native: True Args: createsliver lnrawv2 instageni-v2.rspec Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnrawv2 expires within 1 day(s) on 2012-04-27 23:51:54 UTC Asked https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 to reserve resources. No manifest Rspec returned. *** Fixed physical node: pc2 not available.*** Fixed physical node: pc5 not available.*** Some fixed nodes failed to map*** Fixed physical node: pc2 not available.*** Fixed physical node: pc5 not available.*** Some fixed nodes failed to map*** ERROR: mapper: Unretriable error. Giving up. seed = 1335573845 Physical Graph: 4 Calculating shortest paths on switch fabric. Virtual Graph: 3 Generating physical equivalence classes:3 Type precheck: Type precheck passed. Node mapping precheck: Node mapping precheck succeeded Pruning pclasses. pclass pruning complete: removed 2 pclasses, 1 remain. Type precheck: Type precheck passed. Policy precheck: Policy precheck succeeded Annealing. *** Fixed physical node: pc2 not available. *** Fixed physical node: pc5 not available. *** Some fixed nodes failed to map ASSIGN FAILED: Type precheck passed. Node mapping precheck succeeded Pruning pclasses. pclass pruning complete: removed 2 pclasses, 1 remain. Type precheck passed. Policy precheck succeeded Annealing. *** Fixed physical node: pc2 not available. *** Fixed physical node: pc5 not available. *** Some fixed nodes failed to map INFO:omni: ============================================================ |
|||
#4 | fixed | Requesting link without specifying capacity results in mapper failure, no bandwidth default available. | ||
Description |
Using version?? on 04.30.2012: This issue was discussed on the InstaGENI maillists, entering ticket to track resolution. In a scenario where a sliver is created without specifying the "capacity" value, the createsliver results in a mapper error. Following are the RSpec lines that cause the failure: <link client_id="insta1-and-insta2"> <interface_ref client_id="insta1:if1"/> <interface_ref client_id="insta2:if1"/> <property source_id="insta1:if1" dest_id="insta2:if1"/> <property source_id="insta2:if1" dest_id="insta1:if1"/> </link> The modified "property" lines that resolve the problem: <link client_id="insta1-and-insta2"> <interface_ref client_id="insta1:if1"/> <interface_ref client_id="insta2:if1"/> <property capacity="1000000" source_id="insta1:if1" dest_id="insta2:if1"/> <property capacity="1000000" source_id="insta2:if1" dest_id="insta1:if1"/> </link> The mapper failure reported when using the "property" without a bandwidth specified, is shown here: urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnrawv22 expires within 1 day(s) on 2012-04-30 19:38:59 UTC Asked https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 to reserve resources. No manifest Rspec returned. *** ERROR: mapper: Reached run limit. Giving up. seed = 1335813330 Physical Graph: 4 Calculating shortest paths on switch fabric. Virtual Graph: 3 Generating physical equivalence classes:3 Type precheck: Type precheck passed. Node mapping precheck: Node mapping precheck succeeded Pruning pclasses. pclass pruning complete: removed 2 pclasses, 1 remain. Type precheck: Type precheck passed. Policy precheck: Policy precheck succeeded Annealing. Adjusting dificulty estimate for fixed nodes, 1 remain. Doing melting run Reverting: forced Reverting to best solution Done BEST SCORE: 3.3 in 17000 iters and 0.004363 seconds With 3 violations Iters to find best score: 0 Violations: 3 unassigned: 1 pnode_load: 0 no_connect: 2 link_users: 0 bandwidth: 0 desires: 0 vclass: 0 delay: 0 trivial mix: 0 subnodes: 0 max_types: 0 endpoints: 0 Nodes: insta1 pc1 insta2 pc5 unassigned: tbdelay0 End Nodes Edges: linksdelaysrc/insta1-and-insta2/insta1:0,insta2:0 Mapping Failed linksdelaydst/insta1-and-insta2/insta2:0,insta1:0 Mapping Failed End Edges End solution ASSIGN FAILED: Type precheck passed. Node mapping precheck succeeded Pruning pclasses. pclass pruning complete: removed 2 pclasses, 1 remain. Type precheck passed. Policy precheck succeeded Annealing. Adjusting dificulty estimate for fixed nodes, 1 remain. Doing melting run Reverting: forced Reverting to best solution Done BEST SCORE: 3.3 in 17000 iters and 0.004363 seconds unassigned: 1 pnode_load: 0 no_connect: 2 link_users: 0 bandwidth: 0 desires: 0 vclass: 0 delay: 0 trivial mix: 0 subnodes: 0 max_types: 0 endpoints: 0 |