We need a tool (palybook?) that does preflight checks for hosted-engine deployment checking: - all repos / subscription are correctly enabled - network configuration and connectivity works - storage is reachable and have enough space. The tool may be shipped as standalone script if easier, so it can be run just downloading it from a web page and run on a system without having all needed repos. The tool should allow to fix automatically repos / subscription similarly to hyper-upgrade script.
Can this script be also bonded to Cockpit to be run from there?
(In reply to Nikolai Sednev from comment #1) > Can this script be also bonded to Cockpit to be run from there? Make sense to me on oVirt Node. On non oVirt Node systems it needs to be there before cockpit-ovirt is installed since you'll need the right repos to be enabled in order to install it.
Please provide documentation on how "Pre-flight checks for deployment" should be used, if there any intervention from customer's side is required or the playbook will be automatically run from the engine during deployment or prior deployment.
We have a hosted engine setup role now with tests being anticipated as early as possible on given configuration. We are going to make the role the default way of deploying hosted engine.
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/tree/master/tasks/pre_checks
4.3 deployment failed on old CPU type: orchid-vds1 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 15 Model name: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz Stepping: 6 CPU MHz: 2656.000 CPU max MHz: 2656.0000 CPU min MHz: 1992.0000 BogoMIPS: 5319.62 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0,1 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow dtherm 2019-01-29 12:52:22,572+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [5ed45ea8] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host orchid-vds2-vlan162.qa.lab.tlv.redhat.com moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all Preflight checks cpu list is outdated.
Moving back to assigned forth to comment #7. The CPU type of the host should have been checked before deployment continued and catch up the old CPU type incompatible issue and report it back to customer.
Not blocking ovirt-4.3.0 on this. Moving to 4.3.1.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
We have no capacity for working on this, closing deferred for now. Can be reopened once there will be capacity for handling.