cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Weingärtner (JIRA) <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-8806) Powered off VM's not showing up in WebUI
Date Fri, 17 Mar 2017 17:25:41 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafael Weingärtner closed CLOUDSTACK-8806.
------------------------------------------
       Resolution: Invalid
    Fix Version/s:     (was: Future)

> Powered off VM's not showing up in WebUI
> ----------------------------------------
>
>                 Key: CLOUDSTACK-8806
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8806
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.5.1
>         Environment: CloudStack WebUI 4.5.1 advanced networking
>            Reporter: Matthias Hänni
>            Priority: Minor
>              Labels: easyfix, newbie
>
> Hello I'm new on this jira board.
> But I found a strange behaviour in the Cloudstack WebUI that I like to report:
> Under Home>Infrastructure>Hosts>ESX-ServerXY>Instances
> Only running VM's are shown.
> Even if I select the filter "stopped" I don't see the stopped VM's.
> In this view (Instances on an Esx-Host) the "Filter"-Choices are pretty useless:
> - "All": only showing running VM
> - "mine": I can only access this view as a root-admin
> - "running": shows the same as "all"
> - "stopped": never shows anything, because cloudstack deletes the Info about on what
ESX the VM is registered, directly after the VM is stopped.
> - "destroyed": same as "stopped". A destroyed VM is always stopped and in the cloudstack
DB not assigned to an esx Host



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message