Issues with installing when running behind a web proxy

Issue Background

Daniel Sangorrin reported these issues when attempting to install the beta

Issue description

• I did the following to setup proxy settings for vagrant on Ubuntu 16.04 Xenial:

  $ sudo apt-get remove vagrant <-- gives errors when installing vagrant-proxyconf $ dpkg -i vagrant_1.9.4_x86_64.deb $ vagrant plugin install vagrant-proxyconf $ vi Vagrantfile

• if Vagrant.has_plugin?("vagrant-proxyconf")
• config.proxy.http = "http://xxx:yyyy/"
• config.proxy.https = "https://xxx:yyy/"
• config.proxy.no_proxy = "127.0.0.1,localhost,xxxx."
• end

Q: maybe it would be good to add this to the tutorial

• I got an error during vagrant up

==> default: fatal: [kernel-ci-backend]: FAILED! => {"changed": false, "cmd": "/usr/bin/apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv EA312927", "failed": true,

• Solved it by adding port 80 for apt-key

   $ vagrant ssh
    guest$ vi kernelci-backend/roles/install-deps/tasks/install-mongodb.yml
                - hkp://keyserver.ubuntu.com
	+hkp://keyserver.ubuntu.com:80
     [Alt]  sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927

Q: if that works without proxies, maybe it should be set to 80 by default?

• Modifying the 8080 port (very commonly used port, e.g. Fuego ;_+)

I solved this by $ vi Vagrantfile + config.vm.network :forwarded_port, guest: 8081, host: 8081 $ sudo vi /etc/apache2/ports.conf -> change to 8081 $ sudo vi /etc/apache2/sites-enabled/lava-server.conf -> change to 8081 $ sudo service apache2 restart $ sudo /etc/init.d/lava-server restart

Q: maybe this could be automated (?)

---

Second, regarding to LAVA health checks I think this is again a problem with being behind a proxy but I'm not sure how to debug it. These are the error messages that I get with QEMU's health check (/vagrant/tests/qemu-health-check.yaml)

- log:
    Root tmp directory created at /var/lib/lava/dispatcher/tmp/7
    start: 0 validate
    Validating that https://images.validation.linaro.org/kvm/standard/stretch-2.img.gz exists
    no device environment specified
    Invalid job definition
    Invalid job data: ["HTTPSConnectionPool(host='images.validation.linaro.org', port=443): Max retries exceeded with url: /kvm/standard/stretch-2.img.gz (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f430c9b9c50>: Failed to establish a new connection: [Errno -5] No address associated with hostname',))"]
    validate duration: 0.02
    Cleanup: removing /var/lib/lava/dispatcher/tmp/7
- traceback
    Traceback (most recent call last):
      File "/usr/lib/python2.7/dist-packages/lava/dispatcher/commands.py", line 88, in run_pipeline_job
        job.validate(simulate=validate_only)
      File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/job.py", line 173, in validate
        self.pipeline.validate_actions()
      File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 205, in validate_actions
        raise JobError("Invalid job data: %s\n" % self.errors)
    JobError: Invalid job data: ["HTTPSConnectionPool(host='images.validation.linaro.org', port=443): Max retries exceeded with url: /kvm/standard/stretch-2.img.gz (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f430c9b9c50>: Failed to establish a new connection: [Errno -5] No address associated with hostname',))"]

Acceptance criteria