Hi,
Thanks for your help. We made another test using the API (stopRouter
with force=true) and restart network. All resources have been released.
We need to update the CloudStack's database in the same state as the
VMWare's database (like : VM host, VM state, )
We would like to make this
Ahmad, Alena, you might have some thoughts on Guillaume's email below ?
-sebastien
On Jul 25, 2013, at 1:57 PM, Fraysse Guillaume gfraysse...@gmail.com wrote:
Hello everyone,
We had an unexpected problem on our infrastructure while we were
upgrading CloudStack from 2.2.13 to 4.1
Hey Guillaume, not sure why you have to manually edit the db. After an
upgrade. Assuming you followed the steps in the release notes, you could
make the api call to rebootrouter on all the routers and that should do the
trick of recreating them properly.
On Jul 25, 2013 12:13 PM, Sebastien
