Still a bug in 20.0.0.

Any update on what's happening with this?

OK, I've finally figured out why I was getting confused and what NMS-4562's Description of "You have to delete the service from the node page" means.

If you try to delete a provisioned node from the node page, you see the message that the node has to be deleted from the provisioning group. Thus you would expect that the services also should be deleted from the provisioning group as well and, if you try to delete the service from the node page when the service is still in the Provisioning Group, the deletion request appears to be rejected/ignored. So you wind up have to delete a provisioned service twice, from the provisioning group first (don't forget to synchronize), and then from the node page. From a UI standpoint, it should be clear that requiring a double deletion in two significantly different parts of the user interface is a bug.

Probably what should happen to be consistent with node UI behaviour is that

• on the Node's service page, the Delete link should only available if the service was provisioned. (To avoid having to parse the provisioning group, it probably means adding a flag to the ifservices table to indicate if an interface service was provisioned or not, and have the flag be maintained by the provisioning daemon during synchronization)

• on the Node's service page, a message should be displayed when a service was provisioned that it needs to be removed from the provisioning group

• the process for queuing a deletion should accept an additional parameter to indicate that the request was generated by the provisioning daemon (or it could check the new provisioned flag in the ifservices table)

Duplicate of https://opennms.atlassian.net/browse/NMS-4562#icft=NMS-4562

It is the same issue, I believe, as https://opennms.atlassian.net/browse/NMS-4562#icft=NMS-4562. This is currently a limitation and not a bug. We don't have the ability to know if the services was provisioned or discovered so we don't delete any services no longer defined in the requisition. This should be an enhancement request and marked as a duplicate.

Having same issue here with an NRPE-based service that does not have a detector defined for the requisition group. I've been using opennms for quite some time and have seen this problem in 1.8 branch as well as 1.10.3 (which is what I'm currently using). We usually use psql to remove the service from the node's interface (not really ideal).

I should note that usually when I'm trying to do this there is an existing outage for the service on the node(s) in question (the reason I'm deleting it in the first place). Perhaps there's some constraint in the SQL being used to delete the service that is failing due to a key relationship or something.