
21 Apr
2014
21 Apr
'14
9:50 a.m.
Hi! An upgrade would fix it. The general issue hasn't yet been fixed (looking at BZ 1077110) and I don't know whether it'll be backported when it does. I would edit the engine's DB and append "4.14" to the option_value column of the vdc_options table where option_name="SupportedVDSMVersions", then restart the engine. I think this should be enough. Yours, Lior. On 20/04/14 17:45, Drew Showers wrote:
I know this error has been noted and a BZ bug logged. However, is there a fix or workaround yet for 3.3? Or do I need to upgrade to 3.4?
Thanks in advance!
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users