Using JON 2.4, deleting a VDB through JON GUI inventory removes the vdb from the EDS instance, but does not remove it from inventory. Instead, it shows the vdb as unavailable.
Steps to Reproduce:
1. Deploy a vdb to EDS
2. Have agent report vdb to JON, verify in GUI
3. In JON inventory, delete the vdb
VDB is removed from physical server but remains in JON inventory, just as disabled. It remains there even after running 'discovery -f' from the agent console.
VDB is removed from physical server and removed from JON inventory.
Assigning to Len to retest on JON3
Assigning to Pavel, via Len, to verify if this is still an issue with the latest version of the plugins and JON3
Tested with JON 3.0.0 BETA3, PostgreSQL 8.4.8, OpenJDK 1.6.0, SOA-P/EDS 5.1.0.GA
The VDB deleted from JON is removed physically and from JON inventory too.
Moving to ON_QA now that Pavel says it is ok.
*** Bug 781020 has been marked as a duplicate of this bug. ***
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE