On Mon, Aug 20, 2018 at 4:33 PM, Ralf Schenk <rs@databay.de> wrote:

Hello,

after enabling it, restarting ovirt-engine service and restarting the VM I got back gfapi based Disks:

Am 20.08.2018 um 15:15 schrieb Alex K:

Hi,

On Mon, Aug 20, 2018 at 10:45 AM Ralf Schenk <rs@databay.de> wrote:

Hello,

very interesting output. Feature Lost...

[root@engine-mciii ~]# engine-config -g LibgfApiSupported
LibgfApiSupported: false version: 3.6
LibgfApiSupported: false version: 4.0
LibgfApiSupported: true version: 4.1
LibgfApiSupported: false version: 4.2

Did you enable it? did it fix your issue?

In my opinion these kind of features should be managed automatically when leveraging cluster/dc level, without manual interaction.

Or is it this expected by design that no engine-config feature is automatically propagated when updating cluster/dc level?

I remember something similar happening to me with "UserDefinedVMProperties"

One option could be at least a pop-up showing that there are some engine-config features that the user would lost when raising level....

Gianluca