Tejas created CLOUDSTACK-6979:
---------------------------------
Summary: Not abe to delete virtual router hence network
Key: CLOUDSTACK-6979
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6979
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller, XenServer
Affects Versions: 4.3.0
Environment: CentOS 6.3, Xenserver 6.2 SP1, Cloudstack 4.3,
Reporter: Tejas
Priority: Critical
I have created "DefaultSharedNetworkOffering" with redundant router for guest
network. While trying to recreate the delete the routers one router got deleted
& other was showing in "expunging" state. So I was not able to delete network
also.
While trying to delete the network it was showing below logs,
2014-06-23 13:02:21,589 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Unable to apply ip association,
virtual router is not in the right state Expunging
2014-06-23 13:02:21,594 DEBUG [c.c.n.IpAddressManagerImpl]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Resource is not available:
VirtualRouter
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
unreachable: Unable to apply ip association, virtual router is not in the right
state
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3928)
2014-06-23 13:02:21,595 WARN [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Unable to apply ip address
associations for Ntwk[207|Guest|17] as a part of shutdownNetworkRules
2014-06-23 13:02:21,595 WARN [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Failed to cleanup network id=207
resources as a part of shutdownNetwork
2014-06-23 13:02:21,599 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Sending network shutdown to
VirtualRouter
2014-06-23 13:02:21,601 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Stopping router
VM[DomainRouter|r-27-VM]
2014-06-23 13:02:21,604 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Stopped called on
VM[DomainRouter|r-27-VM] but the state is Expunging
2014-06-23 13:02:21,606 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Network id=207 is shutdown
successfully, cleaning up corresponding resources now.
2014-06-23 13:02:21,654 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Lock is released for network
Ntwk[207|Guest|17] as a part of network shutdown
2014-06-23 13:02:22,045 WARN [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-16:ctx-011048ba ctx-55af37fa) Unable to complete destroy of the
network due to element: VirtualRouter
OR while restarting the network with cleanup checked it says,
ecSt5VOMl2wgsZtnAYbNEfbh8%2Bk%3D&_=1403505273057
2014-06-23 12:04:33,538 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-11:ctx-587064a4) Unexpected exception while executing
org.apache.cloudstack.api.command.user.network.RestartNetworkCmd
com.cloud.exception.InvalidParameterValueException: Network is not in the right
state to be restarted. Correct states are: Implemented, Setup
at
com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImpl.java:1832)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
I did work around for this.
I changed broadcast uri in 'networks' table in cloud db to unused integer. &
removed ip range from UI under exiting network. & I was able to add network
with same vlan,gw & netmask.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
