Thanks Andrei, appreciate your feedback. I'll take a shufti in the DB to change the state and I'll open up a ticket.
On Sun, Feb 23, 2014 at 9:18 PM, Andrei Mikhailovsky <and...@arhont.com>wrote: > Ronald, > > > I've seen this happening since version 3 of CS, so for me it is a know > issue. Not sure what changes the state of Network, but it seems to change > from time to time. The way I deal with it is by changing the database entry > for the network to the right state and it seems to work. > > > Andrei > > ----- Original Message ----- > > From: "ronald higgins" <ronald.higg...@gmail.com> > To: "users" <users@cloudstack.apache.org> > Sent: Sunday, 23 February, 2014 7:07:30 PM > Subject: Network is not in the right state to be restarted. Correct states > are: Implemented, Setup > > Hi All, > > We experienced a storage failure a few days back and Cloudstack has since > recovered (everything is up and running) but the Networks seem to be in a > funny state. They're all in an "Implementing" state. And as such I cannot > restart them. > > I only came across this because I was digging into possible reasons for a > new Load Balancer not actually load balancing. > > Anyone seen this behaviour before in CS 4.2.1 ? Or have any thoughts on how > to correct it? > > "State: Implementing" > > MGMT LOG SNIP: > > ############################# > > 2014-02-23 21:03:06,407 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) > 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:1790) > at > > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > > org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.execute(RestartNetworkCmd.java:92) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:701) > 2014-02-23 21:03:06,411 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) > Complete async job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ], > jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Network > is not in the right state to be restarted. Correct states are: Implemented, > Setup > > ############################# > > Regards > > Ronald > >
