You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/07/11 11:51:48 UTC

[jira] [Commented] (CLOUDSTACK-3465) [Portable IP] [EIP/ELB Zone] NetworkId of the acquired portable IP is showing "Control Network"

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

venkata swamybabu budumuru commented on CLOUDSTACK-3465:
--------------------------------------------------------

In fact, I am seeing different behaviour when tried in multi zone environment. 

I have 2 more advanced zones in the same setup. 

1. adv zone1 :  when portable IP is acquired on an isolated network then the network id it shows is public network uuid
2. adv zone2 :  when portable IP is acquired on an isolated network then the network id it shows is management network uuid
                
> [Portable IP] [EIP/ELB Zone] NetworkId of the acquired portable IP is showing "Control Network"
> -----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3465
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3465
>             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 id # 67cab313c969e5f488d6c0f92f9ec058288a96a0
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce: 
> 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default EIP/ELB network offering. 
> 2. Deploy a VM. 
> 3. By default VM is associated with is_system=1 public ip address 
> 4. Acquire a portable IP and enable static NAT on the portable IP 
> 5. Click on the acquired portable IP and check the network ID of it.
> Observations:
> (i) It shows the network id as the uuid of "Control network" instead of showing the public network uuid.
> mysql> select * from networks where id=202\G
> *************************** 1. row ***************************
>                    id: 202
>                  name: NULL
>                  uuid: 60e08bb1-2f94-45d6-93b6-f7754f9ad78e
>          display_text: NULL
>          traffic_type: Control
> broadcast_domain_type: LinkLocal
>         broadcast_uri: NULL
>               gateway: 169.254.0.1
>                  cidr: 169.254.0.0/16
>                  mode: Static
>   network_offering_id: 3
>   physical_network_id: NULL
>        data_center_id: 1
>             guru_name: ControlNetworkGuru
>                 state: Setup
>               related: 202
>             domain_id: 1
>            account_id: 1
>                  dns1: NULL
>                  dns2: NULL
>             guru_data: NULL
>            set_fields: 0
>              acl_type: NULL
>        network_domain: NULL
>        reservation_id: NULL
>            guest_type: NULL
>      restart_required: 0
>               created: 2013-07-04 04:12:14
>               removed: NULL
>     specify_ip_ranges: 0
>                vpc_id: NULL
>           ip6_gateway: NULL
>              ip6_cidr: NULL
>          network_cidr: NULL
>       display_network: 1
>        network_acl_id: NULL
> Attaching the screenshot of the same.
> attaching all the required logs along with db dump to the 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