Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Admiral UI shows containers as RUNNING despite being actually stopped - refresh issues #231

Closed
lgayatri opened this issue Dec 6, 2017 · 2 comments

Comments

@lgayatri
Copy link

lgayatri commented Dec 6, 2017

Build: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.3.0-rc2-2628-9e2a95b6.ova

Video attached: Admiral-refresh.zip

Containers will be shown by Admiral in RUNNING state despite being actually STOPPED. Refresh on UI does not help, but if a container is specifically selected to go onto its Usages and Properties page, then the status changes correctly.

@sergiosagu @AntonioFilipov @martin-borisov @sflxn

@sergiosagu
Copy link
Contributor

cc @iilieva

@afilipov1
Copy link
Contributor

@lgayatri The issue seems to be related with the VCH.
docker -H tcp://10.197.37.145:2376 --tls ps -a shows that the zen_pike container is UP for 28 hours despite it is run with sleep 45m.
docker -H tcp://10.197.37.145:2376 --tls inspect zen_pike returns that the status is "Status": "exited"
ps.txt
inspect.txt

Opened an issue for that vmware/vic#6921

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants