Uploaded image for project: 'Common Controller SDK'
  1. Common Controller SDK
  2. CCSDK-3500

no onap directory on pod onap-cds-command-executor

XMLWordPrintable

      During configuration python environment when I call a python function from CBA  I got

      [2021-09-03T13:22:18.537+00:00|INFO|network|grpc-default-executor-0] [IN|REST|gRPC://cds-blueprints-processor-grpc:9111/]

      commonHeader {

      timestamp: "2021-09-03T13:22:09.956Z"

      requestId: "d4e51699-2be6-4914-b101-e408d0f182f0"

      subRequestId: "0"

      flag {

      }

      originatorId: "POLICY"

      {color:#333333}}

      actionIdentifiers {

      blueprintName: "clamp-201"

      blueprintVersion: "1.0.0"

      actionName: "execute-scale-down"

      mode: "sync"

      {color:#333333}}

      status {

      code: 500

      errorMessage: "FAILURE : prepare-env : [\"\",\"\\n\",\"WARNING: The directory \'/home/onap/.cache/pip\' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo\'s -H flag.
      nERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: \'/home/onap\'
      nCheck the permissions.
      n
      nWARNING: You are using pip version 20.1.1; however, version 21.2.4 is available.
      nYou should consider upgrading via the \'/opt/app/onap/blueprints/deploy/clamp-201/1.0.0/dc39a4d9-e190-42a7-a43a-ba16d342f7b4/bin/python -m pip install --upgrade pip\' command.\\n\"]"

      message: "failure"

      timestamp: "Fri Sep 03 13:22:18 GMT 2021"

      {color:#333333}}

      Solution is adding /home/onap directory mannually, but this directory should be created during onap user creation. Please precreate this directory when pod is created

       

       

            djtimoney Dan Timoney
            adenisiewicz adenisiewicz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: