Creating sliver with 1 VM at BBN and 1 VM at RENCI results in Error:Exception encountered

[lnevers@bbn.com]

Created a sliver via ExoSM to request one VM from BBN rack and one VM from RENCI rack, which resulted in the following error:

$ ./src/omni.py -a exosm createsliver experiment1 ./exorspec/EG-EXP-4_exp1.rspec 
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
WARNING:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires in <= 3 hours
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires on 2012-05-23 20:28:37 UTC
INFO:omni:Substituting AM nickname exosm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Substituting AM nickname exosm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Creating sliver(s) from rspec file ./exorspec/EG-EXP-4_exp1.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1
INFO:omni:Asked https://geni.renci.org:11443/orca/xmlrpc to reserve resources. Result:
INFO:omni:<!-- Reserved resources for:
	Slice: experiment1
	At AM:
	URL: https://geni.renci.org:11443/orca/xmlrpc
 -->
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:

  Options as run:
		aggregate: exosm
		framework: pgeni
		native: True

  Args: createsliver experiment1 ./exorspec/EG-EXP-4_exp1.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires in <= 3 hours on 2012-05-23 20:28:37 UTC
Asked https://geni.renci.org:11443/orca/xmlrpc to reserve resources. No manifest Rspec returned. ERROR: Exception encountered: java.lang.NullPointerException 
INFO:omni: ============================================================

Attaching the RSpec used, which has been succesfully used in earlier testing.

[lnevers@bbn.com]

According to Ilia this failure was due to the following activity:

On 5/23/12 4:45 PM, Ilia Baldine wrote:

Luisa,

We've encountered some issues related to the development of new features requested by GPO. The ontology models from the new code got deployed into model repo and conflicted with the old code. At this point it is easier for us to test and deploy the new code with new models features than try to back out the ontology changes. Is it OK for you to do your test next week after we're done?

-ilia

Closing ticket. Will re-open if the problem occurs again next week, when I re-run the test.