Description of problem: NVMe-of service was getting created when we try to create service using different pools. Version-Release number of selected component (if applicable): version : cp.stg.icr.io/cp/ibm-ceph/nvmeof-rhel9:1.2.13-2 How reproducible: Steps to Reproduce: 1. Create a pool and service on gw nodes. 2. Create different pool and apply service using it in client node. Actual results: 2 services are getting created. Expected results: As we do not support 2 daemons running on the same node, but what if mistakenly happens at customer(which we do not want to) , we want the GW code to abort deployment with different pool name ( cuz we may apply again with same pool_name for various reasons like GW scaling) with a error message if a node already has a nvmeof service. Additional info:
The issue here is restricting deploying nvmeof service on more than 1 pool for 7.1. We need to see how to restrict this for 7.1.z. For 7.1 we will add this to the RN.