Entries are not getting populated in "Encrypted-KVM" even after successful execution of KVM policy

[sidheshwarc]

Hi,
I am trying to use KVM policy wherein I am trying to use put operation to add entries in "Encrypted-KVM" but I found out that for some API calls the entires(key-value) are getting added in KVM while for others the values are not visible or not getting populated in KVM.

I tested this observation by making 10-15 API calls, in which 4-5 entires didnt appear in KVM but rest did appear. I waited for an hour for this values to get populated but no luck.

Also same is the case with "Delete" operation.

Please could you help me in resolving this issue and letting me know what might be the root cause behing it.

 

[dchiesa1]

When I try to populate things in the KVM, it always works.  Is it possible that you are not using the Scope and Key consistently across your PUT and GET policies?  As one example of what I mean, if you use a Scope of apiproxy in your KVM policy, and the PUT is in a separate API proxy than the GET, then your GET will not retrieve the entry that you wrote via the PUT.   You can also specify a Scope of "policy" which really is "API proxy revision". And that means if you PUT with revision N, then redeploy the proxy so that you get revisoin N+1, then a GET executed within revision N+1 will not retrieve the value that you PUT with revision N.

If you can show me how to reproduce that behavior, I'd be happy to look into your particular problem. "Show me how" means, give me an apiproxy, with at least two  KeyValueMapOperations policies, one a GET and one a PUT, and also give me a sequence of requests to send into the apiproxy....  If you can give me that and it reproduces the "GET doesn't always work" behavior, then I can file a defect on your behalf and we'll get it fixed. I suspect though, that you have a configuration that is not correct.