Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Mon, 12 Nov 2012 13:49:12 +0000 (UTC)
From: "Chip Childers (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <211176679.100378.1352728152410.JavaMail.jiratomcat@arcas>
In-Reply-To: <690269583.100174.1352725632773.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-470) Add vm does not list all vms
 when creating port forwards
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495262#comment-13495262 ] 

Chip Childers commented on CLOUDSTACK-470:
------------------------------------------

You would never want to create a port forwarding rule that targets a VM that will be expunged within some period of time, right?  They are effectively deleted from the system, simply waiting for the cleanup process to do the final delete step.
                
> Add vm does not list all vms when creating port forwards
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-470
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-470
>             Project: CloudStack
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: pre-4.0.0
>         Environment: CS 3.0.2 with KVM, XenServer, VMware
>            Reporter: Jasper Wonnink
>            Priority: Critical
>              Labels: bug, ui
>
> On Network -> Networkname -> IP address -> my IP [Source NAT] -> Port Forwarding
> When adding a port forward it only shows a few instances instead of all available. 
> Request that the api server receives:
> command=listVirtualMachines&response=json&sessionkey=11PcW3amb12ABc8TVL47HJFX36E%3D&page=1&pageSize=20&listAll=true&networkid=529a1461-5a1b-4277-9148-8b47fe79a4b3&_=1352725034341 200 { "listvirtualmachinesresponse" : { "count":20 ,"virtualmachine" :
> This gives me the following list (in the log) filtered by state:
>         "state": "Running",
>         "state": "Running",
>         "state": "Running",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
>         "state": "Destroyed",
> Which is a list of 20 items like requested. However the GUI shows only the 3 running instances no matter what filtering i use (All, Running, Stopped, Destroyed).
> The other VM's that are Running and dont fall into the first 20 will never be displayed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira