Created attachment 1397057 [details] /var/log/ovirt-engine/engine.log Description of problem: This is common practice to mount `/tmp` (and some others) with `noexec`. So, direct call of `/tmp/somescript.sh` will fail, and `/usr/bin/env bash /tmp/somescript.sh` will do the job. Steps to Reproduce: 1. mount -t tmpfs -o noexec tmp /tmp 2. In WebUI: Hosts -> installation -> Check for upgrade Actual results: In events: `Failed to check for available updates on host ov1.buh.gu.kyiv.dsns.gov.ua with message 'Unexpected connection termination`. In engine.log: see attachment. Expected results: Host check for upgrades successfully
This was part of the original design of the deployment process. Martin, how much work is to change the call to theovirt-host-deploy command through ssh issued by the engine? Do we want to change it?
Check for upgrade/Upgrade flow in 4.2 is now performed by Ansible, which is using home directory (which causes issue with vintage node BZ1540101). So we should probably switch to use home directory instead of /tmp, but we will need have an exception for vintage node until we will get rid of it.
(In reply to Martin Perina from comment #2) > Check for upgrade/Upgrade flow in 4.2 is now performed by Ansible, which is > using home directory (which causes issue with vintage node BZ1540101). So we > should probably switch to use home directory instead of /tmp, but we will > need have an exception for vintage node until we will get rid of it. We will not support vintage node in 4.3, since it's < 4.2 cluster level.
Closing as deferred as vintage node will not be supported in 4.3