On 6 Aug 2020, at 00:41, i iordanov <iiordanov@gmail.com> wrote:

Hi Michal,

I dug down enough to see that I could alter the option that specifies the supported CPUs in the database. What would have helped me is a diff of what was removed. Ultimately, I didn't have enough time to dig for the diff, but if you know where it can be found it may be of use for other people that need to use a Penryn based server.

Hi,
the diff is right there, the option value for 4.2 cluster still has it. so you just need that piece (penryn definition) to copy&paste into the 4.4 entry(i think the numbers are then duplicated, but it shouldn’t really matter, cpu name is the "key”)

Thanks,
michal


I was able to swap two systems at my place and get a Nehalem one to use with oVirt, but if I get a chance I may try to revert to the older one since it's a bit more convenient for me to use. I would certainly try updating the DB if I could get the diff where you guys removed the line from the DB seed files.

Cheers and thanks!
iordan

On Tue, Aug 4, 2020 at 4:46 AM Michal Skrivanek <michal.skrivanek@redhat.com> wrote:


On 4 Aug 2020, at 06:10, i iordanov <iiordanov@gmail.com> wrote:

It seems the issue stems from cpu type being empty.

'cpu': {'architecture': 'undefined', 'type': ''}

2020-08-03 23:31:39,888-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 cluster_facts: {'changed': False, 'ansible_facts': {'ovirt_clusters': [{'href': '/ovirt-engine/api/clusters/0eb77d38-d5fe-11ea-8808-00163e42a94a', 'comment': '', 'description': 'The default server cluster', 'id': '0eb77d38-d5fe-11ea-8808-00163e42a94a', 'name': 'Default', 'affinity_groups': [], 'ballooning_enabled': True, 'bios_type': 'cluster_default', 'cpu': {'architecture': 'undefined', 'type': ''}, 'cpu_profiles': [], 'data_center': {'href': '/ovirt-engine/api/datacenters/0ea3b60e-d5fe-11ea-a87c-00163e42a94a', 'id': '0ea3b60e-d5fe-11ea-a87c-00163e42a94a'}, 'enabled_features': [], 'error_handling': {'on_error': 'migrate'}, 'external_network_providers': [], 'fencing_policy': {'enabled': True, 'skip_if_connectivity_broken': {'enabled': False, 'threshold': 50}, 'skip_if_gluster_bricks_up': False, 'skip_if_gluster_quorum_not_met': False, 'skip_if_sd_active': {'enabled': False}}, 'firewall_type': 'firewalld', 'gluster_hooks': [], 'gluster_service': False, 'gluster_volumes': [], 'ha_reservation': False, 'ksm': {'enabled': True, 'merge_across_nodes': True}, 'log_max_memory_used_threshold': 95, 'log_max_memory_used_threshold_type': 'percentage', 'mac_pool': {'href': '/ovirt-engine/api/macpools/58ca604b-017d-0374-0220-00000000014e', 'id': '58ca604b-017d-0374-0220-00000000014e'}, 'memory_policy': {'over_commit': {'percent': 100}, 'transparent_huge_pages': {'enabled': True}}, 'migration': {'auto_converge': 'inherit', 'bandwidth': {'assignment_method': 'auto'}, 'compressed': 'inherit', 'encrypted': 'inherit', 'policy': {'id': '80554327-0569-496b-bdeb-fcbbf52b827b'}}, 'network_filters': [], 'networks': [], 'permissions': [], 'required_rng_sources': ['urandom'], 'scheduling_policy': {'href': '/ovirt-engine/api/schedulingpolicies/b4ed2332-a7ac-4d5f-9596-99a439cb2812', 'id': 'b4ed2332-a7ac-4d5f-9596-99a439cb2812'}, 'switch_type': 'legacy', 'threads_as_cores': False, 'trusted_service': False, 'tunnel_migration': False, 'version': {'major': 4, 'minor': 4}, 'virt_service': True, 'vnc_encryption': False}]}, 'deprecations': [{'msg': "The 'ovirt_cluster_facts' module has been renamed to 'ovirt_cluster_info', and the renamed one no longer returns ansible_facts", 'version': '2.13'}], 'failed': False}

Perhaps this Penryn series CPU is too old for this oVirt installation...

Yes, we dropped Penryn from supported CPU list i 4.3. You could probably stil make it run but it would need messing with engine’s db, adding back Nehalem entry to ServerCPUList(e.g. from 4.2 cluster version line) and resume the deployment somehow.


iordan

On Mon, Aug 3, 2020 at 11:54 PM i iordanov <iiordanov@gmail.com> wrote:
Hi guys,

I am trying to install oVirt 4.4 for testing of the aSPICE and Opaque Android clients and tried to follow this slightly outdated doc:


to deploy an all-in-one self-hosted engine using the command-line.

I started with a clean CentOS 8 installation, set up an NFS server and tested that mounts work from the local host and other hosts, opened all ports with firewalld to my LAN and localhost (but left firewalld enabled).

During the run of 
hosted-engine --deploy
I got the following error:

2020-08-03 23:31:51,426-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 TASK [ovirt.hosted_engine_setup : debug]
2020-08-03 23:31:51,827-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 server_cpu_dict: {'Intel Nehalem Family': 'Nehalem', 'Secure Intel Nehalem Family': 'Nehalem,+sp
ec-ctrl,+ssbd,+md-clear', 'Intel Westmere Family': 'Westmere', 'Secure Intel Westmere Family': 'Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel SandyBridge Family': 'SandyBridge', 'Secure Intel SandyBridge Fa
mily': 'SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel IvyBridge Family': 'IvyBridge', 'Secure Intel IvyBridge Family': 'IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel Haswell Family': 'Haswell-noTSX
', 'Secure Intel Haswell Family': 'Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Broadwell Family': 'Broadwell-noTSX', 'Secure Intel Broadwell Family': 'Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Sk
ylake Client Family': 'Skylake-Client,-hle,-rtm', 'Secure Intel Skylake Client Family': 'Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Skylake Server Family': 'Skylake-Server,-hle,-rtm', 'Secure I
ntel Skylake Server Family': 'Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Cascadelake Server Family': 'Cascadelake-Server,-hle,-rtm,+arch-capabilities', 'Secure Intel Cascadelake Server Family':
 'Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities', 'AMD Opteron G4': 'Opteron_G4', 'AMD Opteron G5': 'Opteron_G5', 'AMD EPYC': 'EPYC', 'Secure AMD EPYC': 'EPYC,+ibpb,+virt-ssbd', 'IB
M POWER8': 'POWER8', 'IBM POWER9': 'POWER9', 'IBM z114, z196': 'z196-base', 'IBM zBC12, zEC12': 'zEC12-base', 'IBM z13s, z13': 'z13-base', 'IBM z14': 'z14-base'}
2020-08-03 23:31:52,128-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Convert CPU model name]
2020-08-03 23:31:52,530-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': "The task includes an option with an undefined variable. The error was: 'dict object' ha
s no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 15, but may\nbe elsewhere in th
e file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n  - debug: var=server_cpu_dict\n              ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task
. Only one syntax may be used.\n", '_ansible_no_log': False}
2020-08-03 23:31:52,630-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. 
The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 
15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n  - debug: var=server_cpu_dict\n              ^ here\n\nThere appears to be both 'k=v' shortha
nd syntax and YAML in this task. Only one syntax may be used.\n"}
2020-08-03 23:31:52,931-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 PLAY RECAP [localhost] : ok: 35 changed: 5 unreachable: 0 skipped: 5 failed: 1
2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:215 ansible-playbook rc: 2
2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:222 ansible-playbook stdout:
2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:225 ansible-playbook stderr:
2020-08-03 23:31:53,033-0400 DEBUG otopi.context context._executeMethod:145 method exception
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/target_vm.py", line 238, in _closeup
    r = ah.run()
  File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run
    raise RuntimeError(_('Failed executing ansible-playbook'))
RuntimeError: Failed executing ansible-playbook
2020-08-03 23:31:53,034-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook

On line 105 of the Ansible config file indicated, there is the following task:
  - debug: var=server_cpu_dict

However, here is a bit more of the file:
  - name: Parse server CPU list
    set_fact:
      server_cpu_dict: "{{ server_cpu_dict | combine({item.split(':')[1]: item.split(':')[3]}) }}"
    with_items: >-
      {{ server_cpu_list.json['values']['system_option_value'][0]['value'].split('; ')|list|difference(['']) }}
  - debug: var=server_cpu_dict
  - name: Convert CPU model name
    set_fact:
      cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}"
  - debug: var=cluster_cpu_model
  - name: Parse emulated_machine
    set_fact:
      emulated_machine:
        emulated_machine_list.json['values']['system_option_value'][0]['value'].replace(
        '[','').replace(']','').split(', ')|first

Exact version of the package that contains the file in question:

ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch

Many thanks for your attention! Please cc me when you reply, as I may not be monitoring the mailing list actively. Happy to provide any other information.

In case it's relevant, the CPU of the machine:

# cat /proc/cpuinfo 
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU           X5460  @ 3.16GHz
stepping : 6
microcode : 0x60f
cpu MHz : 2703.129
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
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 cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6318.15
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

Sincerely,
iordan

-- 
The conscious mind has only one thread of execution.


-- 
The conscious mind has only one thread of execution.
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW6YYORL5YVWHTINM447V5I/



--
The conscious mind has only one thread of execution.