Opened 9 years ago

Last modified 8 years ago

#78 new

AM V3 reports incorrect error for bad credential type (type geni_sfaBROKEN)

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

Description

In a scenario where bad credentials are used (type geni_sfaBROKEN), the aggregate returns the following error:

No resources from AM http://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/3.0:  (Error 
from Aggregate: code 1. protogeni AM code: 1: Malformed arguments: Wrong number of 
credentials (PG error log: urn:publicid:IDN+instageni.gpolab.bbn.com+log+13056).)

The message seem to imply that the wrong number of credentials were given which is not the case.

Change History (1)

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

Problem is unchanged:

No resources from AM http://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/3.0:  (Error from Aggregate: code 1. protogeni AM code: 1: Malformed arguments: Wrong number of credentials (PG log url - look here for details on any failures: https://boss.instageni.gpolab.bbn.com/spewlogfile.php3?logfile=f0cceae221514a91faef071047256ab7).) 

To reproduce "am_api_accept.py -V3 -a am-undertest Test.test_ListResources_badCredential_badtype"

Note: See TracTickets for help on using tickets.