cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirk Kosinski <kirk.kosin...@shapeblue.com>
Subject RE: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue
Date Mon, 06 Jun 2016 23:22:03 GMT
Hi, what is the status of the CPVM and SSVM in the UI?  Were they really upgraded successfully?

Also, are there any errors in the management-server.log?

kirk.kosinski@shapeblue.comĀ 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HS
@shapeblue



-----Original Message-----
From: Cloud List [mailto:cloud-list@sg.or.id] 
Sent: Monday, June 06, 2016 9:51 AM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Upgrading from ACS 4.2 to 4.8 - VR upgrade issue

Hi,

I tried upgrading our CloudStack 4.2.0 on our test environment to 4.8.0, and I am having issues
on VR upgrade. I followed the upgrade instructions at below URL:

http://cloudstack-release-notes.readthedocs.io/ja/stable/upgrade/upgrade-4.2.html

On the last step to restart all the system VMs and VRs, it seems that the cloudstack-sysvmadm
script managed to restart the system VMs (SSVM and
CPVM) but not the VR.

# nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > sysvm.log 2>&1
&

Here's the output of the sysvm.log file:

====
nohup: ignoring input
/usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such file or directory

Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
Done stopping and starting console proxy vm(s) .

Stopping and starting 1 running routing vm(s)...
*ERROR: Failed to restart domainRouter with id 5*

Done restarting router(s).
====

Output of the cloud.log file:

====
[2016.06.05-22.28.40] Stopping and starting 1 secondary storage vm(s)...
[2016.06.05-22.28.40] INFO: Stopping secondary storage vm with id 3 [2016.06.05-22.28.46]
INFO: Starting secondary storage vm with id 3 [2016.06.05-23.29.00] ERROR: Failed to startSystemVm
id=3; jobId is 121c5d89-745a-4e8e-9f96-0b348ef42abf
[2016.06.05-23.29.00] ERROR: Failed to start secondary storage vm with id 3 [2016.06.05-23.29.00]
ERROR: Failed to start secondary storage vm with id 3 [2016.06.05-23.29.00] Done stopping
and starting secondary storage vm(s).
[2016.06.05-23.29.00] Stopping and starting 1 console proxy vm(s)...
[2016.06.05-23.29.00] INFO: Stopping console proxy with id 2 [2016.06.05-23.29.06] INFO: Starting
console proxy vm with id 2 [2016.06.05-23.30.49] Done stopping and starting console proxy
vm(s) .
[2016.06.05-23.30.49] Stopping and starting 1 running routing vm(s)...
[2016.06.05-23.30.49] INFO: Restarting router with id 5 [2016.06.06-00.30.59] ERROR: Failed
to restart domainRouter with id 5; jobId 4a3f681e-c4a6-4856-9d42-0d3b79bffdae
[2016.06.06-00.31.04] Done restarting router(s).
====

Initially I noted that the VR remains in 4.2.0 version (instead of the expected 4.8.0 version),
tried to destroy the router so it'll be recreated but it doesn't get created successfully.

Tried to run the cloudstack-sysvmadm manually with the -r option to restart only the VR, and
the problem still persists.

At the moment, the version of the VR is "UNKNOWN" and the "Require Upgrade"
state is "Yes".

Any advice how to make the VR back up and running?

Looking forward to your reply, thank you.

Cheers.

-ip-
Mime
View raw message