cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jessica Wang (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
Date Tue, 07 Oct 2014 23:11:34 GMT


Jessica Wang updated CLOUDSTACK-3195:
    Attachment: 2014_10_07_jessica3.PNG

> cannot view/delete forward rules if underlying/target VM is destroyed first
> ---------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3195
>                 URL:
>             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
>         Attachments: 2014_10_07_jessica1.PNG, 2014_10_07_jessica2.PNG, 2014_10_07_jessica3.PNG
> 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

View raw message