cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-1762) [MultipleIpsToNic] addIpToNic should not let network id or broadcast to be assigned as secondary ip
Date Thu, 21 Mar 2013 15:35:15 GMT
venkata swamybabu budumuru created CLOUDSTACK-1762:
------------------------------------------------------

             Summary: [MultipleIpsToNic] addIpToNic should not let network id or broadcast
to be assigned as secondary ip
                 Key: CLOUDSTACK-1762
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1762
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Controller
    Affects Versions: 4.2.0
         Environment: commit de1ac4b7cd70424a204b753cb955f3ef26ddd67c

- Advanced zone with xen cluster
            Reporter: venkata swamybabu budumuru
            Assignee: Jayapal Reddy
             Fix For: 4.2.0


Steps to reproduce :

1. create a network with default CIDR 10.1.1.0/24 
2. deploy a virtual machine using the above network
3. try to acquire secondary ips like 10.1.1.0 or 10.1.1.255

Observations :

(i) IP gets assigned as secondary ip to nic without any issues.

http://10.147.59.194:8096/api?command=addIpToNic&nicid=311405d1-5df2-4d18-b880-efba64dd1e34&ipaddress=10.1.1.0

<listnics cloud-stack-version="4.2.0-SNAPSHOT"><count>2</count><nic><id>df903937-994e-4354-8fb5-1d306790d320</id><netmask>255.255.255.0</netmask><gateway>10.1.1.1</gateway><ipaddress>10.1.1.131</ipaddress><isolationuri>vlan://901</isolationuri><broadcasturi>vlan://901</broadcasturi><isdefault>true</isdefault><macaddress>02:00:30:94:00:02</macaddress><secondaryip><id>ad96a3f4-3ce6-4e11-8c3f-d4ac241f4d80</id><ipaddress>10.1.1.156</ipaddress></secondaryip><secondaryip><id>b3ce40a5-de95-4dab-a0db-652f4e457fd0</id><ipaddress>10.1.1.253</ipaddress></secondaryip><secondaryip><id>ccee041d-6844-440b-bd2c-f2685cc40e82</id><ipaddress>10.1.1.255</ipaddress></secondaryip></nic>

Expected Result :

- It should not let network id or broadcast address to vms


attaching vmops.log and api.log to bug

--
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

Mime
View raw message