This was supposed to have been fixed but I'm experiencing it in NCM 7.0.2 and NPM 10.4. Opening at ticket with support now to track Case #424103
So in working with support it was determined that the deletion was failing due to a database timeout when it tried to clean up the config archives. Found that the purge configs job had been disabled and we had upwards to 60 configs for each node (over 350). I set the purge config job to keep only 15 copies and ran. I then re-synced the nodes into NPM and was able to delete successfully. So in my particular case it was simply timing out not anything to do with the previous bug.
I'm running NCM 7.1.1 and when I delete a node in NPM 10.4, it also deletes it from NCM 7.1.1
Have you tried running a node sync and then testing it again?
No...I'm on 7.0.2 I don't want to do a node sync until after support checks...I know the workaround however it's not supposed to do that anymore since upgrading to 7.0.2 so I want them to see what's going on.
Fair enough. I was just wondering if after you do a node sync, if the issue goes away permanently.
I had the same problem but since having done a node sync, it's now no longer a problem.
Gotcha...what's really weird is 7.0.2 fixed this issue for us...and I have deleted several nodes since without issue...This most recent delete is where it reared it's ugly head again.