VCHs and containers that were deleted from the ESXi still being seen in Admiral UI about admiral HOT 3 CLOSED

With the latest image the issue has been fixed.

from admiral.

Can still see the issue on Admiral, if VCH is created using any VIC appliance other than VIC1.5.5.

Tested 2 scenarios:

1st scenario: Deployed 2 VCHs with VIC 1.5.4, created a few containers with each VCH, added the VCHs to a project (project-p01) in Admiral.
After this, upgraded the VIC appliance to VIC1.5.5 and deleted the VCHs using vic-machine-linux delete. But I can still see those 2 VCHs in admiral in the 'ON' state. Note: Did not upgrade the VCH to the new VCH version that came with the VIC 1.5.5

2nd Scenario: Deployed VIC 1.5.5, created 2 VCHs and and some containers, added them to an admiral project and then deleted the VCHs.
This time, in the admiral UI, I can see that the VCHs are in WARNING status and the associated containers are in STOPPED status.

@lazarin @luwang-vmware @renmaosheng

from admiral.

This is because there's some error with the upgrade as in fact it is downgrade and the new admiral is 1.5.0 instead of 1.5.5.

user@vic-st [ / ]# docker images | grep admiral
vmware/admiral     ova          33a6598a5c0d    14 months ago    295MB
vmware/admiral     vic_v1.5.0   33a6598a5c0d    14 months ago    295MB

from admiral.