[jira] [Commented] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on CLOUDSTACK-3195:
-------------------------------------------------------------

Commit 925f30a41b0dc5c4eddf6061852d9e73e9623d99 in cloudstack's branch refs/heads/master from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=925f30a ]

CLOUDSTACK-3195: UI > IP Address > detailView > Configuration tab > Port Forwarding > for regular-user, if underlying VM has been destroyed (i.e. listVirtualMachines API returns nothing), compose vm object from limited vm data in port forwarding rule object. So, a vm object (required in widget code) can be passed to widget code.


> cannot view/delete forward rules if underlying/target VM is destroyed first
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3195
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.1.0
>         Environment: CentOS 6.4+latest patches with official 4.1.0 RPM release from Apache
>            Reporter: Bryan Whitehead
>            Assignee: Jessica Wang
>             Fix For: 4.4.0
>
>
> As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network.
> After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network.
> Verify the forward and firewall rule work (ssh SNAT-IP etc).
> KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN user)
> Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it.
> The admin user can see the bogus rule and delete it. Then everything works as expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)