Chulyoon Jung chulyoon.jung@lge.com writes:
Dear Michael,
Thank you for your reply. I can understand your upgrade procedure.
I have one more question about upgrade. Sometime, I met version conflict like below.
In this case how can I resolve the conflict?
I'm not sure, I've not seen this problem before. What does this print:
/srv/lava/instances/woden/var/lib/bootstrap-venv/bin/python -c 'import pkg_resources; print pkg_resources.require("distribute")[0].version'
? If it doesn't print "0.6.24" perhaps try this command:
/srv/lava/instances/woden/var/lib/bootstrap-venv/bin/pip install \ /srv/lava/.cache/download-cache/dist/distribute-0.6.24.tar.gz
Cheers, mwh
Thank you for your help again.
C. Y. Jung
==================== LAVA Deployment Tool ==================== Installing/upgrading application code from a revision of lp:lava-manifest
- '[' '!' -e /srv/lava/instances/woden/code/rtag:2013.01 ']'
- bzr branch -r tag:2013.01 lp:lava-manifest
/srv/lava/instances/woden/code/rtag:2013.01 Branched 105 revisions.
- mkdir /srv/lava/instances/woden/code/rtag:2013.01/bin
- '[' -d /srv/lava/instances/woden/code/current/local ']'
- find /srv/lava/instances/woden/code/current/local -maxdepth 1 -type l
-exec cp -P '{}' /srv/lava/instances/woden/code/rtag:2013.01/local/ ';'
- ln -s /srv/lava/instances/woden/var/lib/bootstrap-venv/bin/uwsgi
/srv/lava/instances/woden/var/lib/bootstrap-venv/bin/buildout /srv/lava/instances/woden/code/rtag:2013.01/bin/
- ln -s /srv/lava/.cache/download-cache
/srv/lava/instances/woden/code/rtag:2013.01/download-cache
- ln -s /srv/lava/.cache/eggs
/srv/lava/instances/woden/code/rtag:2013.01/eggs ++ basename buildout-production.cfg
- local cfg=buildout-production.cfg
- '[' buildout-production.cfg '!=' buildout-production.cfg ']'
- pushd /srv/lava/instances/woden/code/rtag:2013.01
/srv/lava/instances/woden/code/rtag:2013.01 ~/01_LAVA/201212_release/lava-deployment-tool-2012.11
- /srv/lava/instances/woden/var/lib/bootstrap-venv/bin/buildout -c
buildout-production.cfg Creating directory '/srv/lava/instances/woden/code/rtag:2013.01/parts'. Creating directory '/srv/lava/instances/woden/code/rtag:2013.01/develop-eggs'. Develop: '/srv/lava/instances/woden/code/rtag:2013.01/.' While: Installing. Getting section instance. Initializing section instance. Installing recipe lava-manifest. Error: There is a version conflict. We already have: distribute 0.6.34
-----Original Message----- From: Michael Hudson-Doyle [mailto:michael.hudson@linaro.org] Sent: Monday, February 18, 2013 1:24 PM To: Chulyoon Jung; linaro-validation@lists.linaro.org Cc: bernard.park@linaro.org; ka.chun@lge.com; 'Andy Doan' Subject: Re: [LAVA] question about LAVA instance upgrade
Chulyoon Jung chulyoon.jung@lge.com writes:
Dear validation team,
My name is Chulyoon Jung, LG electronics. I want to know exact procedure for upgrading lava instance according your
release.
As you know, linaro release source code and tools regularly. So, We want our lava server to upgrade as your release (example 13.01).
But, I don't know how I can upgrade each eggs's tool version according
your release.
(currently we use code/r75 and lava-android-test is 0.11) (release 13.01 has code/r112 and lava-android-test is 0.14)
I receive Michael's e-mail.
Yes, I can upgrade to the latest version using this CMD. ./bin/buildout -n
Could you provide the method how I can upgrade lava server as 13.01
release?
You need to make sure that LAVA_BUILDOUT_CFG in your instance's instance.conf file is set to "buildout-production.cfg" and then you can run "./lava-deployment-tool upgrade $instance_name tag:2013.01".
Cheers, mwh