Uploaded image for project: 'Multicloud'
  1. Multicloud
  2. MULTICLOUD-119

MultiCloud not Accepting v2 Token Request Payload

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • Amsterdam Release
    • Amsterdam Release
    • None
    • ONAP vCPE Integration lab.

      During VNF Restart APPC made a token request to MultiCloud utilizing the v2 token request.  The request seems to be accepted by MultiCloud but the payload containing the auth info for v2 was rejected (log entries below).  The request was made in the vCPE Integration lab(APPC 10.12.25.50).

      MultiCloud error when trying to connect using v2:
      2017-10-24 23:08:42,391 | INFO  | provider:restart | Keystone                         | 410 - appc-iaas-adapter - 1.1.0.SNAPSHOT | 1 * Sending client request on thread qtp1412045646-643 - /restconf/operations/appc-provider:restart
      1 > POST http://10.0.14.1:9005/api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2/tokens
      1 > Accept: application/json
      1 > Content-Type: application/json
      {
        "auth" : {
          "tenantId" : "466979b815b5415ba14ada713e6e1846",
          "passwordCredentials" : {
            "username" : "demo",
            "password" : "onapdemo"
          }
        }
      }

      2017-10-24 23:08:42,392 | DEBUG | provider:restart | HttpURLConnection                |  -  -  | sun.net.www.MessageHeader@71674fd29 pairs: {POST /api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2/tokens HTTP/1.1: null}{Accept: application/json}{Content-Type: application/json}{User-Agent: Jersey/2.25.1 (HttpUrlConnection 1.8.0_131)}{Cache-Control: no-cache}{Pragma: no-cache}{Host: 10.0.14.1:9005}{Connection: keep-alive}{Content-Length: 166}
      2017-10-24 23:08:42,394 | DEBUG | provider:restart | HttpURLConnection                |  -  -  | sun.net.www.MessageHeader@6894f1297 pairs: {null: HTTP/1.0 403 Forbidden}{Date: Tue, 24 Oct 2017 23:08:46 GMT}{Server: WSGIServer/0.1 Python/2.7.14}{Vary: Cookie}{X-Frame-Options: SAMEORIGIN}{Content-Type: application/json}{Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS}
      2017-10-24 23:08:42,394 | INFO  | provider:restart | Keystone                         | 410 - appc-iaas-adapter - 1.1.0.SNAPSHOT | 1 * Client response received on thread qtp1412045646-643 - /restconf/operations/appc-provider:restart
      1 < 403
      1 < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
      1 < Content-Type: application/json
      1 < Date: Tue, 24 Oct 2017 23:08:46 GMT
      1 < Server: WSGIServer/0.1 Python/2.7.14
      1 < Vary: Cookie
      1 < X-Frame-Options: SAMEORIGIN
      {"detail":"Authentication credentials were not provided."}

      2017-10-24 23:08:42,395 | ERROR | provider:restart | TenantCache                      | 410 - appc-iaas-adapter - 1.1.0.SNAPSHOT | PALOS0014E Exception OpenStackResponseException (with status code 403 = Forbidden) while processing service request init. Original exception message was:
       Unexpected status received from Openstack {"detail":"Authentication credentials were not provided."}
       Service request state context:
       PROVIDER=OpenStackProvider, PRINCIPAL=demo, METHOD=init, LINE_NUMBER=153, CLASS=org.openecomp.appc.adapter.iaas.impl.ServiceCatalogV2, TENANT=466979b815b5415ba14ada713e6e1846, THREAD=qtp1412045646-643 - /restconf/operations/appc-provider:restart

            sseabolt sseabolt
            sseabolt sseabolt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: