Feature request about VM DB consistency

[JJAA]

I had to reinstall ESXi on 2 hosts, thus manually adding the VM that were in the storages.

B&R 6.5 did not found the matches , I suppose some VM ID had changed, so I edited the issuing jobs by adding the 'new' VMs and then deleting the old one with exact same name.

Jobs run well, but I still get the 'VMname' is no longer processed by this job. Make sure this change is intentional message in the building VM list process.
Next steps are then OK.

Having intentionally deleted the 'ghosts' the message is inappropriate, at least there should be a way to confirm 'I made sure to did so' ?

Thanks for helping to get out of this minor issue, without dealing with http://ec2-23-23-207-47.compute-1.amazo ... 24&t=11612 complexity,

Jean-Jacques

[Gostev]

You will only get this event logged once, so don't worry about it.