This looks like a regression. When a (Remote) Service gets deleted the corresponding Harvester should also be deleted.
This doesn't happen, and if a user tried to register the service again an error is thrown due to the duplicate key for the harvester.
This looks like a regression. When a (Remote) Service gets deleted the corresponding Harvester should also be deleted. This doesn't happen, and if a user tried to register the service again an error is thrown due to the duplicate key for the harvester.