Brian, For some reason, we had to fork asdc_interface.robot script, that’s why it’s not up-to-date, please create a ticket for this and assign it to me. The reasons are hostname resolution are different from HEAT and OOM. Robot can point to HEAT’s VM IP, whereas robot point to the service directly..
Thanks, Alexis > On Jan 11, 2018, at 3:47 PM, FREEMAN, BRIAN D <bf1...@att.com> wrote: > > Alexis, Michael, > > I was using robot ete-k8s.sh from amsterdam release and the version of > asdc_interface.robot in dockerdata-nfs was out of date. > I cant seem to find where it got loaded from since the asdc_interface.robot > wasn’t compatible with the robot testsuite (the return parameter list from > Model Distribution in the testsuite didnt match the number returns by the > asdc-interface so an error of “16:03:12.828 FAIL Cannot set > variables: Expected 6 return values, got 5. > “ was being returned for each model that was distributed. The models did > successful distrubte but robot was failing on the check. When I did a git > clone and copy the asdc_interface.robot to the dockerdata-nfs directory for > robot ete-k8.sh distribute succeeded. > > Is this just something I did in using cd.sh -b amsterdam or something else ? > > Brian > > _______________________________________________ > onap-discuss mailing list > onap-discuss@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-discuss _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
