You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2014/02/11 07:05:19 UTC
[jira] [Closed] (CLOUDSTACK-5332) Network offering don't use new
system offering for router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Koneti closed CLOUDSTACK-5332.
------------------------------------
Verified with the new 4.3 build and the correct offering is selected,hence closing the issue.
> 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
> Assignee: Jessica Wang
> Fix For: 4.3.0
>
>
> 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 or sql insert query, because in sql table named Network_Offering in the column named Service_Offering_ID is null value (default for this column).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)