Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-2516

Can't create the sdnc naming policy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Frankfurt Release
    • Frankfurt Release
    • None
    • None

      Creating the new sdnc policy failed in the new ONAP deployment (21.04).

      Request:

      curl -k -v --silent -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{    "configBody": "{
       \"service\": \"SDNC-GenerateName\", \"version\": \"CSIT\", \"content\":
       { \"policy-instance-name\": \"ONAP_VNF_NAMING_TIMESTAMP\", 
      \"naming-models\": [ { \"naming-properties\": [ { \"property-name\": 
      \"AIC_CLOUD_REGION\" }, { \"property-name\": 
      \"CONSTANT\",\"property-value\": \"ONAP-NF\"}, { \"property-name\": 
      \"TIMESTAMP\" }, { \"property-value\": \"_\", \"property-name\": 
      \"DELIMITER\" } ], \"naming-type\": \"VNF\", \"naming-recipe\": 
      \"AIC_CLOUD_REGION|DELIMITER|CONSTANT|DELIMITER|TIMESTAMP\" }, { 
      \"naming-properties\": [ { \"property-name\": \"VNF_NAME\" }, { 
      \"property-name\": \"SEQUENCE\", \"increment-sequence\": { \"max\": 
      \"zzz\", \"scope\": \"ENTIRETY\", \"start-value\": \"001\", \"length\": 
      \"3\", \"increment\": \"1\", \"sequence-type\": \"alpha-numeric\" } }, {
       \"property-name\": \"NFC_NAMING_CODE\" }, { \"property-value\": \"_\", 
      \"property-name\": \"DELIMITER\" } ], \"naming-type\": \"VNFC\", 
      \"naming-recipe\": 
      \"VNF_NAME|DELIMITER|NFC_NAMING_CODE|DELIMITER|SEQUENCE\" }, { 
      \"naming-properties\": [ { \"property-name\": \"VNF_NAME\" }, { 
      \"property-value\": \"_\", \"property-name\": \"DELIMITER\" }, { 
      \"property-name\": \"VF_MODULE_LABEL\" }, { \"property-name\": 
      \"VF_MODULE_TYPE\" }, { \"property-name\": \"SEQUENCE\", 
      \"increment-sequence\": { \"max\": \"zzz\", \"scope\": \"PRECEEDING\", 
      \"start-value\": \"01\", \"length\": \"3\", \"increment\": \"1\", 
      \"sequence-type\": \"alpha-numeric\" } } ], \"naming-type\": 
      \"VF-MODULE\", \"naming-recipe\": 
      \"VNF_NAME|DELIMITER|VF_MODULE_LABEL|DELIMITER|VF_MODULE_TYPE|DELIMITER|SEQUENCE\"
       } ] } }",    "policyName": "SDNC_Policy.ONAP_VNF_NAMING_TIMESTAMP",    "policyConfigType": "MicroService",    "onapName": "SDNC",    "riskLevel": "4",    "riskType": "test",    "guard": "false",    "priority": "4",    "description": "ONAP_VNF_NAMING_TIMESTAMP"}' 'https://pdp:8081/pdp/api/createPolicy'

      Response:

      "PE200 - System Error: Error occured while attempting perform this operation.. the request may be incorrect or the PAP is unreachable."

      The possible root cause of this problem is that the pod (helm chart) for pdp began to use the new environment variables e.g:

      • PDP_HTTP_USER_ID: Optional: false
      • PDP_HTTP_PASSWORD: Optional: false
      • PDP_PAP_PDP_HTTP_USER_ID: Optional: false
      • PDP_PAP_PDP_HTTP_PASSWORD: Optional: false

      But in the application container (onap-pdp-0) config file /tmp/policy-install/pdp.config have those variables not resolved:

      PDP related properties
      PDP_HTTP_USER_ID=${PDP_HTTP_USER_ID}
      PDP_HTTP_PASSWORD=${PDP_HTTP_PASSWORD}
      PDP_PAP_PDP_HTTP_USER_ID=${PDP_PAP_PDP_HTTP_USER_ID}
      PDP_PAP_PDP_HTTP_PASSWORD=${PDP_PAP_PDP_HTTP_PASSWORD}

            krystian krystian
            krystian krystian
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: