Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A63C810B79 for ; Wed, 3 Jul 2013 14:21:20 +0000 (UTC) Received: (qmail 13086 invoked by uid 500); 3 Jul 2013 14:21:20 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 12952 invoked by uid 500); 3 Jul 2013 14:21:20 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 12945 invoked by uid 500); 3 Jul 2013 14:21:20 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 12942 invoked by uid 99); 3 Jul 2013 14:21:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 14:21:20 +0000 Date: Wed, 3 Jul 2013 14:21:19 +0000 (UTC) From: "Francois Gaudreault (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-3330) Autocaling needs a VR to work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Gaudreault updated CLOUDSTACK-3330: -------------------------------------------- Priority: Major (was: Critical) > Autocaling needs a VR to work > ----------------------------- > > Key: CLOUDSTACK-3330 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3330 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server > Affects Versions: 4.1.0 > Reporter: Francois Gaudreault > > When you create an autoscaling load balancing rule, and the VR for that network haven't been created, you need to spin a VM in order to first create the VR, and then the external LB will be assigned, and the autoscaling will start working. Is this the expected behaviour? I would expect that if you add autoscaling rule, CS would deal with VR creation, and LB assignment. > Steps to reproduce: > - Create an isolated guest network, and select a NetScaler Network Offering > - Create an autoscaling LB rule > (nothing will happen) > - The create a VM on that network, and stuff will start to spin. -- 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