I’m pretty sure that V3 support was added in the Casablanca branch a couple months ago (it introduced some bugs during the backport). There are new varaibles required in integration-override.yaml for it as you would exepct.
https://jira.onap.org/browse/TEST-39 Brian From: Sangeeth G <[email protected]> Sent: Wednesday, December 05, 2018 6:22 AM To: [email protected]; FREEMAN, BRIAN D <[email protected]>; [email protected]; [email protected] Cc: [email protected]; Anandadas Patki <[email protected]>; Milind Jalwadi <[email protected]> Subject: RE: [onap-discuss] Robot ./demo-k8s.sh issue Hi All, I did some research on scripts inside the robot container and got to know that keystone_get_auth.template and keystone_interface.robot are the template and script that is forming the Post Request with v2 api for token generation. So I modified the keystone auth template for post request for v3 and keystone interface robot with auth url for v3, and now the tokens are being generated. But looks like Openstacklibrary.py script for robot looks for key values like access, tenant from the post response that I get for v3. This openstacklibrary script for robot seems to be developed only for v2 for which it fails in getting the values from the V3 post response. Is there any library script for robot for V3 which would help. Please suggest. KEYWORD ${tenants} = OpenstackLibrary . Get Current Openstack Tenant auth Documentation: Get Openstack tenant from the current alias Start / End / Elapsed: 20181205 04:15:15.164 / 20181205 04:15:15.165 / 00:00:00.001 04:15:15.164 TRACE Arguments: [ 'auth' ] 04:15:15.164 FAIL KeyError: 'access' 04:15:15.165 DEBUG Traceback (most recent call last): File "/var/opt/OpenECOMP_ETE/robot/library/eteutils/OpenstackLibrary.py", line 45, in get_current_openstack_tenant return jsonResponse['access']['token']['tenant'] Best Regards, Sangeeth G From: Sangeeth G Sent: Wednesday, December 5, 2018 10:34 AM To: [email protected]<mailto:[email protected]>; '[email protected]' <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: RE: [onap-discuss] Robot ./demo-k8s.sh issue Hi, I did verify inside the container, and the vm_properties file has the correctly injected values of the openstack keystone url. But still looks to be an issue. PS: This is openstack queens and Keystone here solely implements the Identity API v3. Support for Identity API v2.0 has been removed in Queens in favor of the Identity API v3. But the Robot still takes v2. Please suggest. Best Regards, Sangeeth G From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Brian Sent: Tuesday, December 4, 2018 7:18 PM To: [email protected]<mailto:[email protected]>; Sangeeth G <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Robot ./demo-k8s.sh issue HTTP 404 is not found so most likely your openstack url for robot is wrong still. robot: openStackKeyStoneUrl: http://10.12.25.2:5000<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2-3A5000&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YGwSXJnhK7Q4UN_hr48YVsKwFSyHf9R6-pOceODktxo&s=E0loEN_GWLj7tKKk0TbduRsomp-HWspQviZ4irxiaPc&e=> notice for robot there is no /v2.0 or /v2.0/tokens Robot auto-detects v2 vs v3 SO url does have the v2.0 and SO only support v2.0 unless you are either wrapping it or using a build from the Dublin/master branch so: so-openstack-adapter: config: openStackUserName: "demo" openStackKeyStoneUrl: http://10.12.25.2:5000/v2.0<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2-3A5000_v2.0&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YGwSXJnhK7Q4UN_hr48YVsKwFSyHf9R6-pOceODktxo&s=gY1ntATVBWKVBBqVmDa0_uJ1FkY0bgU7UAP9ZYRiL_E&e=> Example integration override is in gerrit under integration/deployment/heat/onap-oom/env/windriver/onap-oom.env https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-oom/env/windriver/onap-oom.env;h=6d471ffa2f30a315a6f78d1cba3575323b4ac2d8;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dintegration.git-3Ba-3Dblob-3Bf-3Ddeployment_heat_onap-2Doom_env_windriver_onap-2Doom.env-3Bh-3D6d471ffa2f30a315a6f78d1cba3575323b4ac2d8-3Bhb-3Drefs_heads_master&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YGwSXJnhK7Q4UN_hr48YVsKwFSyHf9R6-pOceODktxo&s=EHj5AcP2mTH7hR2vC-b2DW_IRo7TXGNgXYac1l7SSK4&e=> Brian From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Sangeeth G Sent: Tuesday, December 04, 2018 7:15 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Robot ./demo-k8s.sh issue Hi, I redeployed the robot with the updated values.yaml and the it connects to the keystone url now, but getting a token issue with error code 404 for which the demo script fails again. Is there any prerequisite step for the token error ? Please suggest. KEYWORD ${resp} = RequestsLibrary . Post Request keystone, ${data_path}, data=${data}, headers=${headers} Documentation: Send a POST request on the session object found using the 03:43:37.335 DEBUG Starting new HTTP connection (1): x.x.x.x 03:43:37.343 DEBUG http:// x.x.x.x:5000<https://urldefense.proofpoint.com/v2/url?u=http-3A__172.21.207.59-3A5000&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=kp7DUtV4M497L-Jjmfh5XLzi4fwKmOlAmnySX-g_H6E&s=BXMJmAWicpb3oSvguuAK4fvoOHfGKxl3Q9Xv3ykqjeY&e=> "POST /v2.0/tokens HTTP/1.1" 404 134 03:43:37.343 DEBUG post response: {"error": {"message": "(http:// x.x.x.x:5000/v2.0/tokens<https://urldefense.proofpoint.com/v2/url?u=http-3A__172.21.207.59-3A5000_v2.0_tokens&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=kp7DUtV4M497L-Jjmfh5XLzi4fwKmOlAmnySX-g_H6E&s=vdQwQZ-7KuROyw1EoBuICmSYOIdcGyT5K8GWAg5uaVk&e=>): The resource could not be found.", "code": 404, "title": "Not Found"}} Best Regards, Sangeeth G From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Morgan Richomme Sent: Tuesday, December 4, 2018 3:28 PM To: Sangeeth G <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Robot ./demo-k8s.sh issue Hi I got the same issue values.yaml is correct robot is a priori well configured as I can run ./e2e-k8s.sh onap health without problems. I wonder if the trace would not be misleading and if there is no call to Keystone v2 API to create resources on the OpenStack. As my OpenStack is based on Queens,Keystone v2 is no more supported. We put in place a wrapper for the SO but not for Robot. [cid:[email protected]] /Morgan Le mardi 04 décembre 2018 à 09:42 +0000, Sangeeth G a écrit : Hi David, I did modified the values.yaml to point to correct keystone url and network and tenant id etc., in the /oom/kubernetes/robot and still I get the same error. Best Regards, Sangeeth G From: Pérez Caparrós David, INI-EAI-INO-COW <[email protected]<mailto:[email protected]>> Sent: Tuesday, December 4, 2018 2:52 PM To: Sangeeth G <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Robot ./demo-k8s.sh issue Hi, it seems that there is a problem with your robot config, e.g. openStackKeyStoneUrl. Check values.yaml under oom/kubernetes/robot David -- David Pérez Caparrós Senior Innovation Engineer Swisscom (Switzerland) [email protected]<mailto:[email protected]> On 4 Dec 2018, at 10:14, Sangeeth G <[email protected]<mailto:[email protected]>> wrote: Hi Team, When I run ./demo-k8s.sh onap init, I get the below error on OOM Beijing . Can you please suggest on the same to overcome this issue. Executing robot tests at log level TRACE ============================================================================== OpenECOMP ETE ============================================================================== OpenECOMP ETE.Robot ============================================================================== OpenECOMP ETE.Robot.Testsuites ============================================================================== OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ... ============================================================================== Initialize Customer And Models | FAIL | ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff66f9fc2d0>: Failed to establish a new connection: [Errno 110] Connection timed out',)) ------------------------------------------------------------------------------ OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed ============================================================================== OpenECOMP ETE.Robot.Testsuites | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed Best Regards, Sangeeth G ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=kp7DUtV4M497L-Jjmfh5XLzi4fwKmOlAmnySX-g_H6E&s=C8unzQUKCkDgc9h-FH8yJSvfh-PLnRwOW998aSvkVlE&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=kp7DUtV4M497L-Jjmfh5XLzi4fwKmOlAmnySX-g_H6E&s=yKFUEnUWRj4uhkOxsy9vR4VpXm8Z58h-uUlZIlE_KUY&e=> internally within TechMahindra. ============================================================================================================================ _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14276): https://lists.onap.org/g/onap-discuss/message/14276 Mute This Topic: https://lists.onap.org/mt/28580947/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
