Hi Lukasz, The policy api component has a limitation in this release where requires you to start fresh with a database if you perform an upgrade, which seems may be the case in your situation as I'm going through your emails, if you have gone from 2.2.3 to 2.2.4 that may be very well be the case that you hit. To recover from the situation, you'll need to start fresh with the policy database when upgrading your installation, so make sure to take down the policy-mariadb pod to start fresh (make sure there is no PV/PVCs left, or leftover data under /dockerdata-nfs/dev-policy/policy-mariadb [check on the name, writing it from top of my head]). Let me know how it goes. Best regards, Jorge
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21267): https://lists.onap.org/g/onap-discuss/message/21267 Mute This Topic: https://lists.onap.org/mt/74652485/21656 Mute #clamp: https://lists.onap.org/mk?hashtag=clamp&subid=2740164 Mute #policy: https://lists.onap.org/mk?hashtag=policy&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
