Currently if a user creates an erasure coded pool with an profile that's not default, a new rule with the same name as the pool is created.
I already investigated the issue and know where the problem lies and how to fix it.
I will first explain why this is happening:
oA creates the pool without the rule first, afterwards the rule will be changed. Ceph will in the meanwhile create the rule as a convenience for easier pool creation on the cli.
To not get into the situation of having this kindly implemented service running, oA will, after my changes are published, create a pool with a specified rule and not change the pool's rule afterwards.