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 44B8F1017D for ; Mon, 2 Dec 2013 13:29:31 +0000 (UTC) Received: (qmail 60819 invoked by uid 500); 2 Dec 2013 13:28:47 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 60797 invoked by uid 500); 2 Dec 2013 13:28:45 -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 60750 invoked by uid 500); 2 Dec 2013 13:28:43 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 60728 invoked by uid 99); 2 Dec 2013 13:28:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Dec 2013 13:28:37 +0000 Date: Mon, 2 Dec 2013 13:28:37 +0000 (UTC) From: "Tomasz Zieba (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-5332) Network offering don't use new system offering for router MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tomasz Zieba created CLOUDSTACK-5332: ---------------------------------------- Summary: Network offering don't use new system offering for router Key: CLOUDSTACK-5332 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5332 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: CloudStack 4.2.0 CitrixXen 6.2 Reporter: Tomasz Zieba Reproduction steps: 1. Create new system offering for Virtual Router. 2. Create new Network Offering. From "System Offering for Router" dropdown list choose VirtualRouter offering you've created in first step. 3. Try to deploy VM choosing newly created network offering. Bug Created network still runs a Virtual Router based on default offering. In database we can see that network offering is related to default system offering for router. Expected result Created network should use new System Offering for Virtual Router. We think that this is a problem with GUI. -- This message was sent by Atlassian JIRA (v6.1#6144)