[
https://issues.apache.org/jira/browse/CLOUDSTACK-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru closed CLOUDSTACK-1895.
--------------------------------------------------
verified it on the latest build using an isolated network with LB provided by
NS, firewall services by Juniper SRX and rest by VR. everything came up fine
and didn't see any issue with place holder nic. closing this issue.
> [External Devices-SRX, NetScaler] Failed to bring up router vm while
> configuring the "place holder" nic
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1895
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1895
> 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 # 4edef1fd305891beb5393b722e96f4a140934f9f
> - advanced zone with 1 Xen Cluster
> Reporter: venkata swamybabu budumuru
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: api.log.tgz, vmops.log.tgz
>
>
> Steps to reproduce :
> 1. Create a Network offering with the following services
> mysql> select * from network_offerings where id=13\G
> *************************** 1. row ***************************
> id: 13
> name: ExternalDevicesOffering
> uuid: 37b39b54-2129-4983-9fc9-3a3c87a48191
> unique_name: ExternalDevicesOffering
> display_text: ExternalDevicesOffering
> nw_rate: NULL
> mc_rate: 10
> traffic_type: Guest
> tags: NULL
> system_only: 0
> specify_vlan: 0
> service_offering_id: NULL
> conserve_mode: 0
> created: 2013-04-02 16:34:08
> removed: NULL
> default: 0
> availability: Optional
> dedicated_lb_service: 0
> shared_source_nat_service: 1
> sort_key: 0
> redundant_router_service: 0
> state: Enabled
> guest_type: Isolated
> elastic_ip_service: 0
> elastic_lb_service: 0
> specify_ip_ranges: 0
> inline: 0
> is_persistent: 0
> mysql> select * from ntwk_offering_service_map where network_offering_id=13;
> +----+---------------------+----------------+---------------+---------------------+
> | id | network_offering_id | service | provider | created
> |
> +----+---------------------+----------------+---------------+---------------------+
> | 46 | 13 | Dhcp | VirtualRouter | 2013-04-02
> 16:34:08 |
> | 50 | 13 | Dns | VirtualRouter | 2013-04-02
> 16:34:08 |
> | 49 | 13 | Firewall | JuniperSRX | 2013-04-02
> 16:34:08 |
> | 53 | 13 | Lb | Netscaler | 2013-04-02
> 16:34:08 |
> | 52 | 13 | PortForwarding | JuniperSRX | 2013-04-02
> 16:34:08 |
> | 51 | 13 | SourceNat | JuniperSRX | 2013-04-02
> 16:34:08 |
> | 47 | 13 | StaticNat | JuniperSRX | 2013-04-02
> 16:34:08 |
> | 48 | 13 | UserData | VirtualRouter | 2013-04-02
> 16:34:08 |
> +----+---------------------+----------------+---------------+---------------------+
> 8 rows in set (0.00 sec)
> 2. create a network using the above network offering.
> 3. deploy a VM connected to above network.
> Observations:
> (i) It failed to deploy router VM which eventually resulted in instance
> deployment failure.
> (ii) Here is the snippet from management server log
> 2013-04-02 12:36:38,344 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-17:job-17) Allocating nics for VM[DomainRouter|r-4-VM]
> 2013-04-02 12:36:38,346 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-17:job-17) Allocating nic for vm VM[DomainRouter|r-4-VM] in
> network Ntwk[204|Guest|13] with requested profile
> NicProfile[0-0-null-null-null
> 2013-04-02 12:36:38,348 DEBUG [db.Transaction.Transaction]
> (Job-Executor-17:job-17) Rolling back the transaction: Time = 10 Name =
> -AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
> called by
> -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-VirtualMachineManagerImpl.allocate:293-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualMachineManagerImpl.allocate:339-VirtualNetworkApplianceManagerImpl.deployRouter:1609-VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork:1527-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork:1911
> 2013-04-02 12:36:38,352 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-17:job-17)
> Lock is released for network id 204 as a part of router startup in
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))]
> 2013-04-02 12:37:00,281 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-17:job-17) Lock is released for network id 204 as a part of
> network implement
> 2013-04-02 12:37:00,286 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-17:job-17) Failed to start instance
> VM[User|ecf6d993-8039-4e61-b447-0ad5ad721f52]
> com.cloud.utils.exception.CloudRuntimeException: Does not support custom ip
> allocation at this time: NicProfile[0-0-null-null-null
> at
> com.cloud.network.guru.ExternalGuestNetworkGuru.allocate(ExternalGuestNetworkGuru.java:196)
> at
> com.cloud.network.NetworkManagerImpl.allocateNic(NetworkManagerImpl.java:1317)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> - Attaching the vmops.log and api.log 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
