Upgrade 2.0 to 2.1

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrade 2.0 to 2.1

BigJim
Trying to upgrade VSM on Ubuntu from 2.0 to 2.1 using ./upgrade.sh
i have tried running with ip and hostname.
syntax is:
sudo ./upgrade.sh --controller vsmc --agent vsm1,vsm2,vsm3

Looks like it is a username issue. upgrade.sh is attempting to ssh and prompting for root@vsm1's password. Shouldn't it be cephuser@vsm1's password?
error is:
Permission denied (publickey,password).
+ ssh -t vsmc 'bash -x -s'
Pseudo-terminal will not be allocated because stdin is not a terminal.

install.sh has a -u parameter and that is where I set my ssh keygen.
sudo ./install.sh -u cephuser -v 2.0

This is a test system of VM's and no load, so I could do a strait upgrade. but what fun would that be. Hope I am missing something in the syntax.

Thanks in advance.

-Jim
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade 2.0 to 2.1

bxzhu
hi Jim,
        Maybe I think you can login as cephuser, then run the upgrade.sh. So it will use the cephuser to ssh the other nodes.
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade 2.0 to 2.1

BigJim
Thanks for the reply.
I am using Ubuntu 14.04. The root account is disabled by default. I am using the cephuser account.
It looks like I could go thru all nodes and enable the root account. I don't know if that would solve the upgrade problem as the original install was under cephuser. Seems like i should be able to adjust the upgrade.sh file to use the current (correct) account.

-Jim
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade 2.0 to 2.1

BigJim
Looks like I solved it.
sudo -u cephuser /home/cephuser/Downloads/2.1.0-336/upgrade.sh
I was in the 2.1.0-336 folder and was running
sudo ./upgrade.sh --controller vsmc --agent vsm1,vsm2,vsm3
and tried
sudo ./upgrade.sh -u cephuser --controller vsmc --agent vsm1,vsm2,vsm3

Corrected syntax

sudo -u cephuser /home/cephuser/Downloads/2.1.0-336/upgrade.sh --controller vsmc --agent vsm1,vsm2,vsm3

This got it to run upgrade.sh correctly.

BUT....

Upgrade went sideways.

vsm.agent.log

INFO [vsm.openstack.common.rpc.common] Connected to AMQP server on 192.168.123.10:5673
INFO [vsm.service] Caught SIGTERM, stopping children
INFO [vsm.service] Caught SIGTERM, exiting
INFO [vsm.service] waiting on 1 children to exit.

Same on vsm.physical.log
 with additional
INFO [vsm.service] Child 42451 exited with status 1


Also doesn't look like apache2 is running. when I sudo service apache2 start
The apache2 configtest failed.
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade 2.0 to 2.1

BigJim
Well like an idiot I did not take a snap shot of my VM. But on physical i would be in the same predicament.

I did get Apache2 to start. vsm-dashboard.conf was missing from the /etc/apache2/conf-available/ directory. I was able to recreate that file from the repository and start apache2 without errors. The dashboard is not found 404.

It looks like the upgrade took out my old install as the all vsm services are "unrecognized services" and re-running the upgrade.sh errors with "pre-upgrade failed with error 1." Also there is no vsm directory in /usr/share/.

mysql is still there and all my ceph nodes are up and healthy. I am going to try to get past this error and get the services re-installed.

**************

Update.

Looks like vsm services were missing.
I manually copied vsmrepo to /opt/ and reinstalled vsm vsm-deploy vsm-dashboard and python-vsmclient. got as far as a login screen, but could never log in.

I am now just going to install 2.1 from scratch will try upgrade again for 2.2