Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
drop changing the folder of unix sockets to read-only from virt-launcher
Previously, the solution for the disappearing unix sockets for VNC (due to QEMU bug) was to have virt-launcher track when the unix socket for VNC connection was created and then make its parent folder read-only. In 944e019, we changed virt-handler to make the parent folder of the unix socket for VNC read-only when a new connection request comes and we find that the unix socket exists. This resolves a race in which a VNC connection is established before virt-launcher manages to change the parent folder of the unix socket read-only. Here we remove the former solution as the latter renders it redundant. As for the upgrade flow, virt-handler is the first to be upgraded (before virt-controller and virt-api) and so when new VMI is launched then for sure virt-handler will handle making that folder to read-only. Signed-off-by: Arik Hadas <[email protected]>
- Loading branch information