The naming service query to policy manager is failing host name
verification. While this issue is under investigation, it can be
worked around by configuring the naming service to disable host
name verification. This requires a new version of the network-name-gen
microservice (1.2.1), and a change to set a new env variable to
disable host name verification (enabled by default if this variable
is unset).
Issue-ID: CCSDK-3501
Signed-off-by: Dan Timoney <dtimoney@att.com>
Change-Id: Ia471cd27ce16b6e79a3ce6708e08c7d5f239feb3
(cherry picked from commit
7ec6cb6b34221a9a2293fbc3c09a89940c8f18bd)
value: "{{ .Values.config.aaiUri }}"
- name: AAI_AUTH
value: "{{ .Values.config.aaiAuth }}"
+ - name: DISABLE_HOST_VERIFICATION
+ value: "{{ .Values.config.disableHostVerification }}"
volumeMounts:
- name: certs
mountPath: /opt/etc/config/aai_keystore
# Application configuration defaults.
#################################################################
# application image
-image: onap/ccsdk-apps-ms-neng:1.2.0
+image: onap/ccsdk-apps-ms-neng:1.2.1
pullPolicy: IfNotPresent
# application configuration
polUrl: https://policy-xacml-pdp:6969/policy/pdpx/v1/decision
polEnv: TEST
polReqId: xx
+ disableHostVerification: true
aaiCertPass: changeit
aaiCertPath: /opt/etc/config/aai_keystore
aaiAuth: QUFJOkFBSQ==