The keystone password should be in appc.properties



provider1.type=OpenStackProvider

provider1.name=OpenStack

provider1.identity=http://192.168.9.24:5000/v3<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.9.24-3A5000_v3&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=xdJELLUGA0FXUhkRZfzU_4EpAHmh-H5R6xJU-6YMWnA&s=SaRe_nuxGfDfhNQoaa5t6LiAzlj-jjRnAV_Fv9vdULk&e=>

provider1.tenant1.name=admin

provider1.tenant1.domain=Default

provider1.tenant1.userid=admin

provider1.tenant1.password=xxxxxx



have you tried to use curl to see if that user/passwd worked?



Taka


From: Bangaru Nagendra Babu <[email protected]>
Sent: Thursday, May 23, 2019 9:46 AM
To: CHO, TAKAMUNE <[email protected]>; [email protected]
Cc: Mudit Simlote <[email protected]>; Devangam Manjunatha 
<[email protected]>
Subject: Re: [ONAP-Discuss][vCPE][APPC] APPC IAAS Adapter cannot perform 
requested service, VM url is invalid


Hi Taka,



Thanks for your reply,



We fixed below issue by updating the selflink url from cloud-region site to 
include tenant-id. Now URL validated successfully.



But  APPC is getting unauthorized when it is requesting to openstack via 
keystone. So, we also tried with multi cloud but encountered same issue. Looks 
like APPC is not using  correct password.



Request from APPC to Keystone:


1 > POST 
http://10.43.228.96:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v3/auth/tokens<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.43.228.96-3A80_api_multicloud_v0_CloudOwner-5FRegionOne_identity_v3_auth_tokens&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=xdJELLUGA0FXUhkRZfzU_4EpAHmh-H5R6xJU-6YMWnA&s=x3AvKjPgO91lCFT98wCBPbfsC0ME-YPZn1Y0id2iUGU&e=>
1 > Accept: application/json
1 > Content-Type: application/json
{
  "auth" : {
    "identity" : {
      "methods" : [ "password" ],
      "password" : {
        "user" : {
          "domain" : {
            "name" : "Default"
          },
          "name" : "admin",
          "password" : "********"
        }
      }
    },
    "scope" : {
      "project" : {
        "domain" : {
          "name" : "Default"
        },
        "name" : "83073115-a618-4ef9-aa04-5a188f6632f4"
      }
    }
  }
}


Response from Keystone to APPC:


2019-05-21T12:23:18,349 | INFO  | sshd-SshServer[5e2579a7]-nio2-thread-1 | 
ServerUserAuthService            | 153 - org.apache.sshd.core - 1.6.0 | Session 
karaf@/127.0.0.1:50822<mailto:karaf@/127.0.0.1:50822> authenticated
2019-05-21T12:23:18,417 | INFO  | appc-dispatcher-1 | Keystone                  
       | 503 - appc-iaas-adapter - 1.4.4 | 1 * Client response received on 
thread appc-dispatcher-1
1 < 401
1 < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
1 < Connection: keep-alive
1 < Content-Type: text/html; charset=utf-8
1 < Date: Tue, 21 May 2019 12:23:18 GMT
1 < Server: openresty
1 < Transfer-Encoding: chunked
1 < Vary: Cookie
1 < X-Frame-Options: SAMEORIGIN
{"error":{"message":"The request you have made requires 
authentication.","code":401,"title":"Unauthorized"}}

2019-05-21T12:23:18,417 | ERROR | appc-dispatcher-1 | TenantCache               
       | 503 - appc-iaas-adapter - 1.4.4 | An error occurred when initializing 
cache
com.att.cdp.exceptions.AuthorizationException: PALOS0014E Exception 
OpenStackResponseException (with status code 401 = Unauthorized) while 
processing service request init. Original exception message was:
 Unexpected status received from Openstack {"error":{"message":"The request you 
have made requires authentication.","code":401,"title":"Unauthorized"}}
 Service request state context:
 PROVIDER=OpenStackProvider, PRINCIPAL=admin, METHOD=init, LINE_NUMBER=169, 
CLASS=org.onap.appc.adapter.iaas.impl.ServiceCatalogV3, 
TENANT=83073115-a618-4ef9-aa04-5a188f6632f4, THREAD=appc-dispatcher-1
        at 
com.att.cdp.openstack.util.ExceptionMapper.mapResponseException(ExceptionMapper.java:119)
 ~[?:?]
        at 
com.att.cdp.openstack.util.ExceptionMapper.mapException(ExceptionMapper.java:75)
 ~[?:?]
        at 
org.onap.appc.adapter.iaas.impl.ServiceCatalogV3.init(ServiceCatalogV3.java:187)
 ~[?:?]


W.r.t helm charts of APPC component, we are sure that we are providing correct 
user credentials. What could be the possible issue and please provide your 
valuable inputs upon the same.



Thanks & regards,

Nagendra babu B,

Associate Engineer,

L&T technology services,

Bangalore.




________________________________
From: CHO, TAKAMUNE <[email protected]<mailto:[email protected]>>
Sent: Tuesday, May 21, 2019 9:43 PM
To: [email protected]<mailto:[email protected]>; Bangaru 
Nagendra Babu
Cc: Mudit Simlote; Devangam Manjunatha
Subject: RE: [ONAP-Discuss][vCPE][APPC] APPC IAAS Adapter cannot perform 
requested service, VM url is invalid


On your appc.properties, make sure those are correct from openstack horizon gui.



provider1.type=OpenStackProvider

provider1.name=OpenStack

provider1.identity=http://192.168.9.24:5000/v3<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.9.24-3A5000_v3&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=xdJELLUGA0FXUhkRZfzU_4EpAHmh-H5R6xJU-6YMWnA&s=SaRe_nuxGfDfhNQoaa5t6LiAzlj-jjRnAV_Fv9vdULk&e=>

provider1.tenant1.name=admin

provider1.tenant1.domain=Default

provider1.tenant1.userid=admin

provider1.tenant1.password=root123



http://controller:8774/v2.1/servers/19982f9f-5370-42c5-a9bc-99bf79f528bb<https://urldefense.proofpoint.com/v2/url?u=http-3A__controller-3A8774_v2.1_servers_19982f9f-2D5370-2D42c5-2Da9bc-2D99bf79f528bb&d=DwQFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=l7WtnzxrMmXhiMQWWTKAycxEgpAQoELQscaHhMPrlvM&s=d8a0JBICrIvVmNx-lkRgQmNEtHPdEYZfM-t1vMMxwX8&e=>
 the "controller" should match the provider1.identity etc. and looks like 
tenant id are missing in that url.



so your provider1 should be like 
http://controler:5000/v3<https://urldefense.proofpoint.com/v2/url?u=http-3A__controler-3A5000_v3&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=xdJELLUGA0FXUhkRZfzU_4EpAHmh-H5R6xJU-6YMWnA&s=dH32r5bLSrtBLYF-55frFlx3J6FHG3S6gW8xLsHZZ58&e=>
 or use ip address vice versa.



invalid url error sounds like your dns resolver can't resolve the hostname: 
controller.



Taka



From: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>> On Behalf Of 
Bangaru Nagendra Babu
Sent: Friday, May 17, 2019 10:50 AM
To: [email protected]<mailto:[email protected]>
Cc: Mudit Simlote <[email protected]<mailto:[email protected]>>; 
Devangam Manjunatha 
<[email protected]<mailto:[email protected]>>
Subject: [ONAP-Discuss][vCPE][APPC] APPC IAAS Adapter cannot perform requested 
service, VM url is invalid



Hi team,



    We are trying for vCPE usecase with onap casablanca release. We encountered 
an issue of "APPC unable to restart- invalid url"  while restarting vGMUX.



ERR from APPC:



appc-iaas-adapter - 1.4.4 | APPC0041E APPC IAAS Adapter cannot perform 
requested service, VM url 
[http://controller:8774/v2.1/servers/19982f9f-5370-42c5-a9bc-99bf79f528bb<https://urldefense.proofpoint.com/v2/url?u=http-3A__controller-3A8774_v2.1_servers_19982f9f-2D5370-2D42c5-2Da9bc-2D99bf79f528bb&d=DwQFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=l7WtnzxrMmXhiMQWWTKAycxEgpAQoELQscaHhMPrlvM&s=d8a0JBICrIvVmNx-lkRgQmNEtHPdEYZfM-t1vMMxwX8&e=>]
 is invalid



APPC0090A Operation "App-C IaaS Adapter:Restart" for VNF type 
"83073115-a618-4ef9-aa04-5a188f6632f4" from Source 
"d4e36844-847d-4062-892a-6b0ad7d71020" with RequestID 
"d4e36844-847d-4062-892a-6b0ad7d71020" was started at "2019-05-17T12:16:40Z" 
and ended at "2019-05-17T12:16:41Z" with status code "401"



    We verified that the vGMUX-id (VMID) that the appc is trying to restart is 
correct and  "VNF_DG_MAPPING" mapping table is as expected with restart row for 
"Generic Restart" DG with 3.0.0. Addition of DNS entry for "controller" in 
/etc/hosts of APPC POD is already done.



    Please let us know what could be causing this issue and help us resolve.

    Logs for appc,policy-drools and appc.properties are attached.



    Thanks in advance,



Thanks & regards,

Nagendra babu B,

Associate Engineer,

L&T technology services,

Bangalore.





L&T Technology Services Ltd

www.LTTS.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.LTTS.com&d=DwQFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=l7WtnzxrMmXhiMQWWTKAycxEgpAQoELQscaHhMPrlvM&s=SN-NELYY7Lzz2ReLVN72Y7Xt8XVby1cKcTvm5UXaRh0&e=>

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.



L&T Technology Services Ltd

www.LTTS.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.LTTS.com&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=xdJELLUGA0FXUhkRZfzU_4EpAHmh-H5R6xJU-6YMWnA&s=eFhGrZBdg1AG0kOu9k1VjwglhSXh7TWigckILvCQGZw&e=>

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#17221): https://lists.onap.org/g/onap-discuss/message/17221
Mute This Topic: https://lists.onap.org/mt/31697273/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to