Thanks, all
The migrate commands works for me.
What I did was mainly like following, not sure where is wrong: 1. ./lava-deployment-tool install buildout 2. ./lava-deployment-tool manage buildout createsuperuser 3. add the stream/device-type/device from the administration web page 4. mkdir /srv/lava/code 5. cd /srv/lava/code 6. bzr branch lp:lava-android-test && bzr branch lp:lava-scheduler && bzr branch lp:lava-dashboard 7. source /srv/lava/instances/buildout/bin/activate 8. lava-develop-local lava-android-test && lava-develop-local lava-scheduler && lava-develop-local lava-dashboard 9. sudo stop lava-instance LAVA_INSTANCE=buildout && sudo start lava-instance LAVA_INSTANCE=buildout 10. sudo stop lava-instance-scheduler LAVA_INSTANCE=buildout && sudo start lava-instance-scheduler LAVA_INSTANCE=buildout
Thanks, Yongqin Liu
On 11 October 2012 05:47, Michael Hudson-Doyle michael.hudson@linaro.orgwrote:
Andy Doan andy.doan@linaro.org writes:
On 10/10/2012 06:02 AM, YongQin Liu wrote:
Hi, Michael
When I use lava-tool submit-job to submit a job to my local lava instance (with the buildout format), I get the "Specified device not found" error like this:
(trunk2)18:54:05 liuyq:code$ lava-tool submit-jobhttp://admin:b9w73ap9lox1nxt6rwgsiz17wjsfcr8yu2i7qm7r7eztcj5kpfkhna0lq9rbx4z...
/var/www/images/workspace/jobs/job_cts.json EXPERIMENTAL - SUBJECT TO CHANGE (See --experimental-notice for more info) ERROR: <Fault 404: 'Specified device not found.'> (trunk2)18:54:18 liuyq:code$When I access the administration web page to check the device, I get the "column lava_scheduler_app_devicetype.use_celery does not exist" error like follwoing:
<snip>
I guess this is because I did the the update with wrong method, Do you know if I can fix this problem with some commands? I guess if we can make the django create the database correctly, this problem will go. but I don't know how to do that:(
I'm not sure how you got to this point. However, I *think* you can get your database back to a sane state by running:
lava-server manage migrate
This should get the proper database tables/columns in place to eliminate the error you described.
Yes, running migrate is the right thing to do here.
Cheers, mwh