QA » openQA Project

One question, what about the option to run tests in constrained network environment? Like BS workers?
The similar problem is when using TAP devices instead qemu user network, so there should be a note in docs that administrator is to provide DNS.

BS workers have no network at all - and I think it's pretty boring to test functionality without network. But the problem here is that we try to work around DNS and that fails, so requiring DNS is ok. The problem is that it needs to work within VM - even at times when network setup failed. That was the idea behind it.

Apart cgi-proxy or tiny http server ideas, what about using libguestfs?
e.g. standardize that all logs should end up in /var/tmp/openqa/logs (in the VM). Then, after tests finish, they are moved to testresults directory on worker directly from VM disk (e.g. by using guestfs).

this only works for cases where yast already installed. And you need to know a lot about the disk setup the test did - i.e. RAID,LVM,cryptlvm, ...

I think our easiest solution still is relying on DNS - and only if we get a real problem with it switch back to localhost and proxying.

even the DNS solution is problematic. The scheduler allows upload_log route only for "allowed_hosts". This would be yet another thing to configure to add a new remote worker - not good ;(

So we need to introduce a shared secret.

https://github.com/os-autoinst/os-autoinst/pull/123 is the result - openQA worker will need to move back the uploaded logs from pool dir