cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9779) Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing rule
Date Tue, 28 Feb 2017 09:55:45 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887696#comment-15887696
] 

ASF GitHub Bot commented on CLOUDSTACK-9779:
--------------------------------------------

Github user niteshsarda commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1978#discussion_r103415320
  
    --- Diff: server/test/resources/createNetworkOffering.xml ---
    @@ -34,22 +34,23 @@
                 <ref bean="transactionContextBuilder" />
                 <ref bean="actionEventInterceptor" />
             </list>
    -    </property>
    -  </bean>
    -
    -    <bean id="nicIpAliasDaoImpl" class="com.cloud.vm.dao.NicIpAliasDaoImpl" />
    -    <bean id="ConfigurationManager" class="com.cloud.configuration.ConfigurationManagerImpl">
    -        <property name="name" value="ConfigurationManager"/>
    -    </bean>
    -
    -    <bean class="org.apache.cloudstack.networkoffering.ChildTestConfiguration" />
    +    </property>
    +  </bean>
    +
    +    <bean id="nicIpAliasDaoImpl" class="com.cloud.vm.dao.NicIpAliasDaoImpl" />
    +    <bean id="ConfigurationManager" class="com.cloud.configuration.ConfigurationManagerImpl">
    +        <property name="name" value="ConfigurationManager"/>
    +    </bean>
    +
    +    <bean class="org.apache.cloudstack.networkoffering.ChildTestConfiguration" />
         <bean id="UservmDetailsDaoImpl" class="com.cloud.vm.dao.UserVmDetailsDaoImpl"
/>
         <bean id="hostGpuGroupsDaoImpl" class="com.cloud.gpu.dao.HostGpuGroupsDaoImpl"
/>
    -    <bean id="vGPUTypesDaoImpl" class="com.cloud.gpu.dao.VGPUTypesDaoImpl" />
    -    <bean id="usageEventDaoImpl" class="com.cloud.event.dao.UsageEventDaoImpl" />
    -    <bean id="usageEventDetailsDaoImpl" class="com.cloud.event.dao.UsageEventDetailsDaoImpl"
/>
    -    <bean id="storagePoolHostDaoImpl" class="com.cloud.storage.dao.StoragePoolHostDaoImpl"
/>
    +    <bean id="vGPUTypesDaoImpl" class="com.cloud.gpu.dao.VGPUTypesDaoImpl" />
    +    <bean id="usageEventDaoImpl" class="com.cloud.event.dao.UsageEventDaoImpl" />
    +    <bean id="usageEventDetailsDaoImpl" class="com.cloud.event.dao.UsageEventDetailsDaoImpl"
/>
    +    <bean id="storagePoolHostDaoImpl" class="com.cloud.storage.dao.StoragePoolHostDaoImpl"
/>
         <bean id="primaryDataStoreDaoImpl" class="org.apache.cloudstack.storage.datastore.db.PrimaryDataStoreDaoImpl"
/>
    +    <bean id="loadBalancerVMMapDaoImpl" class="com.cloud.network.dao.LoadBalancerVMMapDaoImpl"
/>
    --- End diff --
    
    This is the only line, I have added in this file. Other changes were not visible in the
patch which was created before committing the changes in local.


> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing
rule
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9779
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9779
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Nitesh Sarda
>
> ISSUE 
> =================
> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing
rule
> REPRO STEPS
> ==================
> 1. Create two isolated guest networks with same CIDR
> 2. Deploy VMs on both networks
> 3. Acquire secondary IP on NICs of both VMs and make sure they have the same value, user
can input the IP address.
> 4. Configure Loadbalancing rule on one of the secondary IP address and try releasing
the other secondary IP address.
> 5. The operation would fail
> EXPECTED BEHAVIOR
> ==================
> Secondary IP address should be released if there are no LB rules associated with it.
> ACTUAL BEHAVIOR
> ==================
> Releasing secondary IP address even if there are no LB rules associated with it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message