[ovirt-users] oVirt 4.1 - the VDSM host was found in a failed state - iptables related ?

[Joseph Kelly]

Hello,

We've just deployed the ovirt-4.1 hosted_engine and I have noticed 2 things that it would be great if people can comment on:

1) It seems that iptables is a hard requirement:

> iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: no

[ INFO  ] Connecting to the Engine
[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
[ ERROR ] The VDSM host was found in a failed state. Please check engine and bootstrap installation logs.
[ ERROR ] Unable to add example-host.tradingscreen.com to the manager
[ INFO  ] Saving hosted-engine configuration on the shared storage domain
[ INFO  ] Shutting down the engine VM

Here is a bug report from 3.5.0 with this exact error:

Bug 1167074<https://bugzilla.redhat.com/show_bug.cgi?id=1167074> - [hosted-engine] Deployment fails with "The VDSM host was found in a failed state. Please check engine and bootstrap installation logs."

Previously, iptables-services was not a required package during hosted-engine deployment, so hosted-engine was unable to configure iptables. Now, iptables-services is
required, so hosted-engine can configure iptables correctly.

2) We have to add new storage to the default domain before the hosted_engine storage domain is imported. So is this happening because of the iptables issue in # 1 above ?
Or is adding this new storage to the default domain also a hard requirement ? Ideally we'd like the hosted_storage to be the Data Master and not have to create stub storage for this.

Here is a bug report from 3.6.1 with this exact error:

Bug 1293928<https://bugzilla.redhat.com/show_bug.cgi?id=1293928>  Cause: importing the nfs domain could interleave with the engine restart as a result of installation.

Consequence: the hosted engine domain won't be imported or activated on the engine setup, and the engine vm wouldn't be imported and displayed in the webadmin or REST.

Fix: Exclusively lock the import attempt so interleaving of 2 imports is impossible and prevent starting the import if there is no DATA domain and an ACTIVE DC.
Note: this means that in order to see the engine VM a user must first import a DATA domain and activate the DC.

Result: the hosted engine domain is imported and the hosted engine VM.

Thanks,
Joe.

--


J. Kelly
Infrastructure Engineer
TradingScreen
www.tradingscreen.com<http://www.tradingscreen.com>

Follow TradingScreen on Twitter, Facebook, or our blog, Trading Smarter

This message is intended only for the recipient(s) named above and may
contain confidential information. If you are not an intended recipient,
you should not review, distribute or copy this message. Please notify
the sender immediately by e-mail if you have received this message in
error and delete it from your system.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170222/12dcdc93/attachment-0001.html>