The config container is fetching the Policy drools parser for Beijing, not Amsterdam, which generates parsing errors in Policy that make it unusable. This happens in config/pe/push-policies.sh, line 9:

wget -O cl-amsterdam-template.drl [ https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl|https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/_closedLoopControlName_.drl]

It should be:

wget -O cl-amsterdam-template.drl [ https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl?h=amsterdam|https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/_closedLoopControlName_.drl?h=amsterdam]

Note ?h=amsterdam at the end. The affected file in the OOM repo is ${OOM_HOME}/kubernetes/config/docker/init/src/config/policy/opt/policy/config/pe/push-policies.sh.

So far it worked because the two parsers were identical. A few days ago, Policy Team modified the Beijing parser, which now creates a mismatch when used with Amsterdam-released dockers. Also, the config container generates this file:

/dockerdata-nfs/onap-ms/policy/opt/policy/config/pe/brmsgw.conf

which contains BRMS_DEPENDENCY_VERSION=1.1.1. This parameter is OK for the Policy Amsterdam Release, but not OK for the maintenance release, which is supposed to be 1.1.3