we are currently working on the integration of the pythonsdk-tests for Guilin.
The new framework support the GR_API.
I am currently able to onboard a new model and detcts that it is properly distributed.
Then I launch an installation "a la carte" and I got from the SO telling that there is SDNC error.
 

}}
 
Before the merge of SDNC Guilin dockers, I did not have this error
 
When I have a look at the SDNC logs I can see lots of java exceptions including one that could explain the AAI related message
020-09-28T16:08:39,697 | WARN  | qtp1382614020-6814 | AbstractAuthenticator            | 147 - org.apache.shiro.core - 1.3.2 |  -   | Authentication failed for token submission [org.apache.shiro.authc.UsernamePasswordToken - admin, rememberMe=false].  Possible unexpected error? (Typical or expected login exceptions should extend from AuthenticationException).
org.opendaylight.aaa.api.AuthenticationException: UserName / Password not found
at org.opendaylight.aaa.shiro.idm.IdmLightProxy.dbAuthenticate(IdmLightProxy.java:106) ~[?:?]
at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Unknown Source) ~[?:?]
 
 
in the SO (bpmn) I can see
020-09-28T16:04:44.061Z|53f531d4-e31c-4ed1-9d26-0b8bd04924f1|camundaTaskExecutor-2|SDNC||||ERROR|500||RA_RESPONSE_FROM_SDNC Error from SDNC: Service eb0aa061-82f0-4b5f-877e-14fac8dfc7d7 is not found BPMN 300 Error from SDNC: Service eb0aa061-82f0-4b5f-877e-14fac8dfc7d7 is not found
2020-09-28T16:04:44.061Z|53f531d4-e31c-4ed1-9d26-0b8bd04924f1|camundaTaskExecutor-2|SDNC||||ERROR|500||Did not receive a successful response from SDNC.
org.onap.so.client.exception.BadResponseException: Error from SDNC: Service eb0aa061-82f0-4b5f-877e-14fac8dfc7d7 is not found