resource-manager ERR in NSOUtil redeploy: Custom service leveraging resource-manager bundled with example-packages(../example-packages/ncs-5.5-resource-manager-3.5.4.tar.gz) generates an error during IP address allocation (service redeploy).Service requires an ID and IP address from the resource-manager pools. ID allocation works as expected, IP allocation fails as per below:ERROR in ncs-java-vm.log:NSOUtil redeploy: re-deploying /ncs:services/ODNL3:ODNL3{demo} as user admin (tid: 38552, type: DEFAULT, trans: true) %s/touch<ERROR> 20-Oct-2021::11:51:29.289 IPAddressAllocator$RequestThread pool-38-thread-1: -java.lang.ClassCastException: class com.tailf.conf.ConfList cannot be cast to class com.tailf.conf.ConfObjectRef (com.tailf.conf.ConfList and com.tailf.conf.ConfObjectRef are in unnamed module of loader 'app') at com.tailf.pkg.ipaddressallocator.IPAddressAllocator.allocateAddress(IPAddressAllocator.java:359) ~ at com.tailf.pkg.ipaddressallocator.IPAddressAllocator$RequestThread.run(IPAddressAllocator.java:1968) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.lang.Thread.run(Thread.java:834) Package has identical package-meta-data.xml with corresponding CCO release for 5.5.2, but underlying code differs (NSOUtil.java).When using the CCO resource-manager, custom service produces no errors and successfully is allocated both ID and IP.Code for allocations in custom service:34 pool_name = "LoopbackIDPool"35 _sync = False36 allocation_name = allocation_prefix + _serviceName3738 id_result = id_allocator.id_request(service,39 _serviceNode,40 tctx.username,41 pool_name,42 allocation_name,43 _sync)66 pool_name = "LoopbackIPPool"67 cidr = 3268 allocation_name = allocation_prefix + <em>serviceName + '</em>' + dev_name + '_' + str(allocation_loopbackID)6970 ip_allocator.net_request(service,71 _serviceNode,72 tctx.username,73 pool_name,74 allocation_name,75 cidr)Let me know if you need additional info. 
We have created a jira ticket for this Issue internally and added it to the release notes.Continue using the RM from CCO for the external package development since current example package has the bug.Release post 3.0 should contain the fix for this issue.We have created a jira ticket for this Issue internally and added it to the release notes.Continue using the RM from CCO for the external package development since current package in the bundle has the bug.Release post 3.0 should contain the fix for this issue.