On Sat, Oct 19, 2013 at 11:57:38AM -0700, Jason Brooks wrote:
Some further 3.3.1 beta tests:
Since I wasn't able to upgrade from 3.3.0.1 (seems related to bz1005533) I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That worked fine, but I wasn't able to add an additional host, and tried with F19 and CentOS 6.4. In both cases, engine complained of: "java.io.IOException: Unexpected connection termination"
I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency issue:
Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta) Requires: selinux-policy-targeted >= 3.7.19-213 Installed: selinux-policy-targeted-3.7.19-195.el6_4.12.noarch (@updates)
I did a clean install of a non-AIO engine on CentOS 6.4, but wasn't able to add a host due to the selinux issue (w/ CentOS) and the "Unexpected connection termination" (w/ F19).
So, so far, F19 AIO w/ no additional hosts is the only 3.3.1 config I've managed to get working.
Thanks for opening a bug on this https://bugzilla.redhat.com/show_bug.cgi?id=1021147 It blocks on Bug 1015068 - Current selinux policy prevents running a VM with volumes under /var/run/vdsm/storage which frankly - I do not know what holds. On the mean time, the only remedy I have is to --force vdsm's installation before firing AIO and to manually tweak the policy with sudo semanage fcontext -a -s system_u -t virt_var_run_t -r s0 '/var/run/vdsm(/.*)