Thank you, motty.
I am also running kvm. Since that time I failed upgrade, I am still
using 4.2.1. I'll try as your advice.
On 29/04/14 05:19 PM, motty cruz wrote:
Stevenllang,
I had the similar issue with VR, I notice it was because I leave the
default system specs on the VR, for instance by default 500MHz on CPU and
128MB on RAM, if you upgrade to at least 1GB on CPU and 512MB of RAM your
VR will survive the upgrade from 4.2.1 to 4.3.1.
I am running KVM, when I upgrade from 4.2.1 to 4.3 my VMs were not able to
access outside world, even if I created a new router.
wish you the best,
-motty
On Tue, Apr 29, 2014 at 2:13 PM, stevenliang <[email protected]> wrote:
Yes, I had two zones(one is basic, another is advanced mode).
After I upgraded from 4.2.1 to 4.3, the vrouter lost.
So I rolled back to 4.2.1, the vrouter came back.
On 29/04/14 04:54 PM, Ian Young wrote:
Did rolling back to 4.2 fix the problem?
On Tue, Apr 29, 2014 at 1:22 PM, stevenliang <[email protected]>
wrote:
I met your situation before. Finally I rolled back to 4.2
On 29/04/14 04:18 PM, Ian Young wrote:
I destroyed the old virtual router and was able to create a new one by
adding a new instance. However, this new router also failed to start,
citing the same error. After that, the expungement delay elapsed and
the
virtual router was expunged, so now I have none.
On Mon, Apr 28, 2014 at 8:52 PM, Ian Young <[email protected]>
wrote:
I upgraded from 4.2.1 to 4.3.0 tonight, following the instructions
here:
http://docs.cloudstack.apache.org/projects/cloudstack-
release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3
At the last step, I tried to restart the system VMs. The virtual
router
failed to start. Here is the message that was displayed in the web UI:
Resource [Host:1] is unreachable: Host 1: Unable to start instance due
to
Unable to start VM[DomainRouter|r-4-VM] due to error in finalizeStart,
not
retrying
I tried running the script to restart the VMs but this time it failed
to
start the console proxy:
[root@virthost1 ~]$ cloudstack-sysvmadm -d 192.168.100.6 -u cloud -p
-a
Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)
Stopping and starting 1 console proxy vm(s)...
ERROR: Failed to start console proxy vm with id 2
Done stopping and starting console proxy vm(s) .
Stopping and starting 0 running routing vm(s)...
Is there a way to wipe the system VMs out and start over?
