You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "manasaveloori (JIRA)" <ji...@apache.org> on 2013/12/02 10:24:35 UTC
[jira] [Commented] (CLOUDSTACK-5273) Applying static Nat by
selecting the VM using List view under static Nat configuration page is
making CS inaccessible.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836382#comment-13836382 ]
manasaveloori commented on CLOUDSTACK-5273:
-------------------------------------------
Applies the same for VPC networks as well
> Applying static Nat by selecting the VM using List view under static Nat configuration page is making CS inaccessible.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5273
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5273
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.3.0
> Reporter: manasaveloori
> Assignee: Brian Federle
> Priority: Critical
> Fix For: 4.3.0
>
>
> Steps:
> 1. Have CS with any HV.
> 2. Deploy a View VM.
> 3. Go to the network and acquire an IP.
> 4. Configure static nat->while selecting the VM we are having 2 options ,one is list view[checkbox] and another is radio button.
> 5. Select the VM using list view[checkbox] on left side and click apply
> Observation:
> Static nat rule will not get applied but the CS gets hanged and the following is the error shown in fire bug.
> 200 OK 1.39s jquery.js (line 7829)
> TypeError: args.context.instances[0] is undefined
> virtualmachineid: args.context.instances[0].id
--
This message was sent by Atlassian JIRA
(v6.1#6144)