[ovirt-devel] design flaw in ovirt

Sven Kieske S.Kieske at mittwald.de
Fri Jun 20 09:53:24 UTC 2014

Am 20.06.2014 11:34, schrieb Dan Kenigsberg:
> I do not quite understand the problem you describe.

See below, I hope this clears some things up.

> Does the problem go away if you set your network to "non-required"? If
> your VM's app does not strictly require unintermitant networking, just
> set the networ to non-required.  Flipping the default of requiredness
> can be considered only for 4.0 ("required" was our default since ever,
> other users' scripts may depend on that).

I know you can't simply switch the default behaviour, and yes, at least
according to the documentation setting the network to "non-required"
should mitigate the issue.

however, the default is, to set every network as "required" without
indicating this to the user in the first place (and the consequences
of this not advertised behaviour).

> Could you attach Vdsm and Engine logs to the bug? How was the host
> fenced?

the host was not fenced, the vms where fenced.

here is a link to the documentation which should explain what I mean:


this is about a single host in a cluster - ovirt can't even fence
single hosts in a single cluster yet, see my other bug report for this:

I could provide logs if they are really necessary, but I doubt they are.
This is documented behaviour, but it is poorly designed, as described
in the BZ.

The fencing mechanism is really buggy / not helpful, see
also this (not really related) bug:

Mit freundlichen Grüßen / Regards

Sven Kieske

Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

More information about the Devel mailing list