Force Health check of a device return "500 Internal Server Error" on localhost

Bug #1301551 reported by Soumya Basak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Dispatcher
Invalid
Undecided
Unassigned

Bug Description

the issue observed when Lava installation on local host from the doc page

https://validation.linaro.org/static/docs/deployment-tool.html

2. deploying a qemu devices:

https://validation.linaro.org/static/docs/qemu-deploy.html?highlight=qemu

   # create a directory for the devices.
   # mkdir /srv/lava/instances/<INST>/etc/lava-dispatcher/devices/
   # /srv/lava/instances/<INST>/etc/lava-dispatcher/devices/qemu01.conf
   device_type = qemu

3. first add a “qemu” device type by going to a URL like:

http://localhost/admin/lava_scheduler_app/devicetype/

4. http://localhost/scheduler/ show the device.

5. once the health check job is submited in http://localhost/admin/lava_scheduler_app/devicetype/qemu/ it not started.

6. when click on force health check (http://localhost:9090/scheduler/device/qemu01/forcehealthcheck) it throwing error: 500 Internal Server Error.

Please refer to the attached snapshot.

Revision history for this message
Soumya Basak (soumya-basak) wrote :
summary: - Force Health check of a device return "500 Internal Server Error"
+ Force Health check of a device return "500 Internal Server Error" on
+ localhost
Revision history for this message
Tyler Baker (tyler-baker) wrote :

Can you post the JSON for you health check?

I am not able to reproduce this behavior locally.

Revision history for this message
Soumya Basak (soumya-basak) wrote :

Hi Tyler,

Here is the JSON for health check:

{
  "timeout": 18000,
  "job_name": "qemu-test",
  "device_type": "qemu",

  "actions": [
    {
      "command": "deploy_linaro_image",
      "parameters": {
        "image": "file:///tmp/beagle-nano.img.gz"
        }
    },
    {
      "command": "boot_linaro_image"
    }
  ]
}

Please correct me, if I am doing any wrong here.

Revision history for this message
Soumya Basak (soumya-basak) wrote :

It fixed the issue after did the following steps.

./lava-deployment-tool remove testserver
./lava-deployment-tool setup testserver
./lava-deployment-tool install testserver
./lava-deployment-tool manage testserver createsuperuser
sudo start lava-instance LAVA_INSTANCE=testserver
restart apache2

closing this bug.

Fathi Boudra (fboudra)
Changed in lava-dispatcher:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.