Can you please open a bug about this?
Il giorno mer 10 giu 2020 alle ore 20:21 Angel R. Gonzalez <
angel.gonza...@uam.es> ha scritto:
> Hello!
> Thanks for your answers.
>
> First, I try to modify 01_create_target_hosted_engine_vm.yml file with
> the below code, and Redeploy. The process don't run. I've typed the code
> again with carefully, and the result is same. I've eliminated the code
> and Redeploy start again until find the error.
>
> After this, I've checked the mails with subject: Issues deploying
> 4.4.with HE on new EPYC hosts, and I think that is a problem with AMD
> processors.
>
> The scenario:
> serverlabs-engine -> 8x Intel(R) Xeon(R) CPU E5410 @ 2.33GHz. This node
> execute wizard Hosted engine
> serverlabs-node2 -> 8x Intel(R) Xeon(R) CPU E31230 @ 3.20GHz. This node
> has configured glusterfs storage
> Both CentOS-8.1.1911-x86_64 ISO LIVE DVD
> kernel 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Apr 9 13:49:54 UTC 2020
> x86_64 x86_64 x86_64 GNU/Linux
>
> # rpm -q qemu-kvm libvirt
> qemu-kvm-4.1.0-23.el8.1.x86_64
> libvirt-5.6.0-10.el8.x86_64
>
> The process running in host node (serverlabs-engine) in storage phase
> deployment:
>
> qemu 8455 1 52 17:46 ? 00:31:09 /usr/libexec/qemu-kvm
> -name guest=HostedEngineLocal,debug-threads=on -S -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/master-key.aes
>
> -machine pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off -cpu
> Penryn,vme=on,ss=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc-adjust=on,arch-capabilities=on,skip-l1dfl-vmentry=on,kvmclock=on
>
> -m 8192 -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1
> -uuid 4af397d7-4c81-4044-934f-90138288e09a -no-user-config -nodefaults
> -chardev socket,id=charmonitor,fd=37,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
> -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot
> menu=off,strict=on -device
> pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
>
> -device
> pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1
> -device
> pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2
> -device
> pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3
> -device
> pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4
> -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 -drive
> file=/var/tmp/localvmaodqdyv8/images/6c7c4d4b-9c11-485d-98e0-466a09888515/c16b87ac-f9d4-491d-a972-7dc333a324a0,format=qcow2,if=none,id=drive-virtio-disk0
>
> -device
> virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>
> -drive
> file=/var/tmp/localvmaodqdyv8/seed.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on
>
> -device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0 -netdev
> tap,fd=39,id=hostnet0,vhost=on,vhostfd=40 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:5a:57:25,bus=pci.1,addr=0x0
>
> -chardev pty,id=charserial0 -device
> isa-serial,chardev=charserial0,id=serial0 -chardev
> socket,id=charchannel0,fd=41,server,nowait -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
>
> -vnc 127.0.0.1:0 -device VGA,id=video0,vgamem_mb=16,bus=pcie.0,addr=0x1
> -object rng-random,id=objrng0,filename=/dev/random -device
> virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.4,addr=0x0 -sandbox
> on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
> -msg timestamp=on
>
>
>
> Finally, I've searched server_cpu_list and server_cpu_dist from
> ovirt-hosted-engine-setup-ansible-create_target_vm-2020510182419-vkgvze.log
>
> file:
>
>
> 2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var
> "he_graphics_device" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""vnc""
> 2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var
> "he_vm_name" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""HostedEngine""
> 2020-06-10 18:24:22,516+0200 DEBUG var changed: host "localhost" var
> "he_host_name" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value:
> ""serverlabs-engine""
> 2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var
> "he_console_type" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""vnc""
> 2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var
> "he_cpu_type" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""model_Penryn""
> 2020-06-10 18:24:22,517+0200 DEBUG var changed: host "localhost" var
> "he_smtp_server" type "<class
> 'ansible.parsing.yaml.objects.AnsibleUnicode'>" value: ""localhost""
> ....
> ....
> .....
> 2020-06-10 18:24:26,064+0200 DEBUG var changed: host "localhost" var
> "ansible_mounts" type "<class 'list'>" value: "[
> {
> "block_available": 43397299,
> "block_size": 4096,
> "block_total": 51343866,
> "block_used": 7946567,
> "device": "/dev/sda1",
> "fstype": "ext4",
> "inode_available": 13025816,
> "inode_total": 13107200,
> "inode_used": 81384,
> "mount": "/",
> "options": "rw,seclabel,relatime",
> "size_available": 177755336704,
> "size_total": 210304475136,
> "uuid": "f3e6d8f4-3ef7-4468-acdf-307119c4570f"
> },
> {
> "block_available": 25747103,
> "block_size": 4096,
> "block_total": 26201600,
> "block_used": 454497,
> "device": "serverlabs-node2:/engine",
> "fstype": "fuse.glusterfs",
> "inode_available": 52428090,
> "inode_total": 52428800,
> "inode_used": 710,
> "mount":
> "/rhev/data-center/mnt/glusterSD/serverlabs-node2:_engine",
> "options":
>
> "rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072",
> "size_available": 105460133888,
> "size_total": 107321753600,
> "uuid": "N/A"
> }
> ]"
> ....
> ....
> ....
> 2020-06-10 18:25:10,736+0200 INFO ansible task start {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_task': 'ovirt.hosted_engine_setup : Get server CPU list via
> REST API'}
> 2020-06-10 18:25:10,736+0200 DEBUG ansible on_any args TASK:
> ovirt.hosted_engine_setup : Get server CPU list via REST API kwargs
> is_conditional:False
> 2020-06-10 18:25:10,737+0200 DEBUG ansible on_any args localhostTASK:
> ovirt.hosted_engine_setup : Get server CPU list via REST API kwargs
> 2020-06-10 18:25:18,877+0200 DEBUG var changed: host "localhost" var
> "server_cpu_list" type "<class 'dict'>" value: "{
> "changed": false,
> "connection": "close",
> "content": "{\n \"values\" : {\n \"system_option_value\" : [
> {\n \"value\" : \"1:Intel Nehalem
> Family:vmx,nx,model_Nehalem:Nehalem:x86_64; 2:Secure Intel Nehalem
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Nehalem:Nehalem,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 3:Intel Westmere Family:aes,vmx,nx,model_Westmere:Westmere:x86_64;
> 4:Secure Intel Westmere
> Family:aes,vmx,spec_ctrl,ssbd,md_clear,model_Westmere:Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 5:Intel SandyBridge Family:vmx,nx,model_SandyBridge:SandyBridge:x86_64;
> 6:Secure Intel SandyBridge
> Family:vmx,spec_ctrl,ssbd,md_clear,model_SandyBridge:SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 7:Intel IvyBridge Family:vmx,nx,model_IvyBridge:IvyBridge:x86_64;
> 8:Secure Intel IvyBridge
> Family:vmx,spec_ctrl,ssbd,md_clear,model_IvyBridge:IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 9:Intel Haswell Family:vmx,nx,model_Haswell-noTSX:Haswell-noTSX:x86_64;
> 10:Secure Intel Haswell
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Haswell-noTSX:Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 11:Intel Broadwell
> Family:vmx,nx,model_Broadwell-noTSX:Broadwell-noTSX:x86_64; 12:Secure
> Intel Broadwell
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Broadwell-noTSX:Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 13:Intel Skylake Client
> Family:vmx,nx,model_Skylake-Client:Skylake-Client,-hle,-rtm:x86_64;
> 14:Secure Intel Skylake Client
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Client:Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm:x86_64;
>
> 15:Intel Skylake Server
> Family:vmx,nx,model_Skylake-Server:Skylake-Server,-hle,-rtm:x86_64;
> 16:Secure Intel Skylake Server
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Server:Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm:x86_64;
>
> 17:Intel Cascadelake Server
> Family:vmx,model_Cascadelake-Server:Cascadelake-Server,-hle,-rtm,+arch-capabilities:x86_64;
>
> 18:Secure Intel Cascadelake Server
> Family:vmx,md-clear,mds-no,model_Cascadelake-Server:Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities:x86_64;
>
> 1:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4:x86_64; 2:AMD
> Opteron G5:svm,nx,model_Opteron_G5:Opteron_G5:x86_64; 3:AMD
> EPYC:svm,nx,model_EPYC:EPYC:x86_64; 4:Secure AMD
> EPYC:svm,nx,ibpb,ssbd,model_EPYC:EPYC,+ibpb,+virt-ssbd:x86_64; 1:IBM
> POWER8:powernv,model_POWER8:POWER8:ppc64; 2:IBM
> POWER9:powernv,model_POWER9:POWER9:ppc64; 1:IBM z114,
> z196:sie,model_z196-base:z196-base:s390x; 2:IBM zBC12,
> zEC12:sie,model_zEC12-base:zEC12-base:s390x; 3:IBM z13s,
> z13:sie,model_z13-base:z13-base:s390x; 4:IBM
> z14:sie,model_z14-base:z14-base:s390x;\",\n \"version\" :
> \"4.4\"\n } ]\n },\n \"name\" : \"ServerCPUList\",\n \"href\" :
> \"/ovirt-engine/api/options/ServerCPUList\",\n \"id\" :
> \"ServerCPUList\"\n}",
> "content_encoding": "identity",
> "content_type": "application/json",
> "cookies": {},
> "cookies_string": "",
> "correlation_id": "57f2a968-5a87-40e7-9b95-d97c4c398bb5",
> "date": "Wed, 10 Jun 2020 16:25:18 GMT",
> "elapsed": 6,
> "failed": false,
> "json": {
> "href": "/ovirt-engine/api/options/ServerCPUList",
> "id": "ServerCPUList",
> "name": "ServerCPUList",
> "values": {
> "system_option_value": [
> {
> "value": "1:Intel Nehalem
> Family:vmx,nx,model_Nehalem:Nehalem:x86_64; 2:Secure Intel Nehalem
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Nehalem:Nehalem,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 3:Intel Westmere Family:aes,vmx,nx,model_Westmere:Westmere:x86_64;
> 4:Secure Intel Westmere
> Family:aes,vmx,spec_ctrl,ssbd,md_clear,model_Westmere:Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 5:Intel SandyBridge Family:vmx,nx,model_SandyBridge:SandyBridge:x86_64;
> 6:Secure Intel SandyBridge
> Family:vmx,spec_ctrl,ssbd,md_clear,model_SandyBridge:SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 7:Intel IvyBridge Family:vmx,nx,model_IvyBridge:IvyBridge:x86_64;
> 8:Secure Intel IvyBridge
> Family:vmx,spec_ctrl,ssbd,md_clear,model_IvyBridge:IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 9:Intel Haswell Family:vmx,nx,model_Haswell-noTSX:Haswell-noTSX:x86_64;
> 10:Secure Intel Haswell
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Haswell-noTSX:Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 11:Intel Broadwell
> Family:vmx,nx,model_Broadwell-noTSX:Broadwell-noTSX:x86_64; 12:Secure
> Intel Broadwell
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Broadwell-noTSX:Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear:x86_64;
>
> 13:Intel Skylake Client
> Family:vmx,nx,model_Skylake-Client:Skylake-Client,-hle,-rtm:x86_64;
> 14:Secure Intel Skylake Client
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Client:Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm:x86_64;
>
> 15:Intel Skylake Server
> Family:vmx,nx,model_Skylake-Server:Skylake-Server,-hle,-rtm:x86_64;
> 16:Secure Intel Skylake Server
> Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Server:Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm:x86_64;
>
> 17:Intel Cascadelake Server
> Family:vmx,model_Cascadelake-Server:Cascadelake-Server,-hle,-rtm,+arch-capabilities:x86_64;
>
> 18:Secure Intel Cascadelake Server
> Family:vmx,md-clear,mds-no,model_Cascadelake-Server:Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities:x86_64;
>
> 1:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4:x86_64; 2:AMD
> Opteron G5:svm,nx,model_Opteron_G5:Opteron_G5:x86_64; 3:AMD
> EPYC:svm,nx,model_EPYC:EPYC:x86_64; 4:Secure AMD
> EPYC:svm,nx,ibpb,ssbd,model_EPYC:EPYC,+ibpb,+virt-ssbd:x86_64; 1:IBM
> POWER8:powernv,model_POWER8:POWER8:ppc64; 2:IBM
> POWER9:powernv,model_POWER9:POWER9:ppc64; 1:IBM z114,
> z196:sie,model_z196-base:z196-base:s390x; 2:IBM zBC12,
> zEC12:sie,model_zEC12-base:zEC12-base:s390x; 3:IBM z13s,
> z13:sie,model_z13-base:z13-base:s390x; 4:IBM
> z14:sie,model_z14-base:z14-base:s390x;",
> "version": "4.4"
> }
> ]
> }
> },
> "msg": "OK (unknown bytes)",
> "redirected": false,
> "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1c mod_wsgi/4.6.4
> Python/3.6",
> "status": 200,
> "transfer_encoding": "chunked",
> "url":
> "
> https://cluster-serverlabs/ovirt-engine/api/options/ServerCPUList?version=4.4
> ",
> "vary": "Accept-Encoding"
> }"
> 2020-06-10 18:25:18,877+0200 INFO ansible ok {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_host': 'localhost', 'ansible_task': 'Get server CPU list via
> REST API', 'task_duration': 8}
> 2020-06-10 18:25:18,878+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33589bac8> kwargs
> ...
> ...
> ...
> 2020-06-10 18:25:29,029+0200 INFO ansible ok {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_host': 'localhost', 'ansible_task': 'Prepare for parsing server
> CPU list', 'task_duration': 0}
> 2020-06-10 18:25:29,029+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3359262b0> kwargs
> 2020-06-10 18:25:29,535+0200 INFO ansible task start {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_task': 'ovirt.hosted_engine_setup : Parse server CPU list'}
> 2020-06-10 18:25:29,535+0200 DEBUG ansible on_any args TASK:
> ovirt.hosted_engine_setup : Parse server CPU list kwargs
> is_conditional:False
> 2020-06-10 18:25:29,536+0200 DEBUG ansible on_any args localhostTASK:
> ovirt.hosted_engine_setup : Parse server CPU list kwargs
> 2020-06-10 18:25:29,589+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586b128> kwargs
> 2020-06-10 18:25:29,600+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586b048> kwargs
> 2020-06-10 18:25:29,611+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3358436d8> kwargs
> 2020-06-10 18:25:29,622+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335936d68> kwargs
> 2020-06-10 18:25:29,633+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335752d68> kwargs
> 2020-06-10 18:25:29,645+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586bdd8> kwargs
> 2020-06-10 18:25:29,656+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3359946d8> kwargs
> 2020-06-10 18:25:29,667+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3359940b8> kwargs
> 2020-06-10 18:25:29,678+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980710> kwargs
> 2020-06-10 18:25:29,689+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335605978> kwargs
> 2020-06-10 18:25:29,701+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586b0f0> kwargs
> 2020-06-10 18:25:29,713+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33588fc88> kwargs
> 2020-06-10 18:25:29,724+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335994eb8> kwargs
> 2020-06-10 18:25:29,736+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980b70> kwargs
> 2020-06-10 18:25:29,747+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980208> kwargs
> 2020-06-10 18:25:29,759+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980710> kwargs
> 2020-06-10 18:25:29,771+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33588f6a0> kwargs
> 2020-06-10 18:25:29,786+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3356dfb38> kwargs
> 2020-06-10 18:25:29,797+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335994ba8> kwargs
> 2020-06-10 18:25:29,808+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586b8d0> kwargs
> 2020-06-10 18:25:29,821+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335752128> kwargs
> 2020-06-10 18:25:29,832+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3357524a8> kwargs
> 2020-06-10 18:25:29,844+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc33586bfd0> kwargs
> 2020-06-10 18:25:29,856+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335994908> kwargs
> 2020-06-10 18:25:29,868+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980518> kwargs
> 2020-06-10 18:25:29,880+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335980780> kwargs
> 2020-06-10 18:25:29,892+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335994240> kwargs
> 2020-06-10 18:25:29,904+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3356dfef0> kwargs
> 2020-06-10 18:25:30,387+0200 DEBUG var changed: host "localhost" var
> "server_cpu_dict" type "<class 'dict'>" value: "{
> "AMD EPYC": "EPYC",
> "AMD Opteron G4": "Opteron_G4",
> "AMD Opteron G5": "Opteron_G5",
> "IBM POWER8": "POWER8",
> "IBM POWER9": "POWER9",
> "IBM z114, z196": "z196-base",
> "IBM z13s, z13": "z13-base",
> "IBM z14": "z14-base",
> "IBM zBC12, zEC12": "zEC12-base",
> "Intel Broadwell Family": "Broadwell-noTSX",
> "Intel Cascadelake Server Family":
> "Cascadelake-Server,-hle,-rtm,+arch-capabilities",
> "Intel Haswell Family": "Haswell-noTSX",
> "Intel IvyBridge Family": "IvyBridge",
> "Intel Nehalem Family": "Nehalem",
> "Intel SandyBridge Family": "SandyBridge",
> "Intel Skylake Client Family": "Skylake-Client,-hle,-rtm",
> "Intel Skylake Server Family": "Skylake-Server,-hle,-rtm",
> "Intel Westmere Family": "Westmere",
> "Secure AMD EPYC": "EPYC,+ibpb,+virt-ssbd",
> "Secure Intel Broadwell Family":
> "Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear",
> "Secure Intel Cascadelake Server Family":
>
> "Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities",
> "Secure Intel Haswell Family":
> "Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear",
> "Secure Intel IvyBridge Family":
> "IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear",
> "Secure Intel Nehalem Family": "Nehalem,+spec-ctrl,+ssbd,+md-clear",
> "Secure Intel SandyBridge Family":
> "SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear",
> "Secure Intel Skylake Client Family":
> "Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm",
> "Secure Intel Skylake Server Family":
> "Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm",
> "Secure Intel Westmere Family":
> "Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear"
> }"
> 2020-06-10 18:25:30,387+0200 INFO ansible ok {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_host': 'localhost', 'ansible_task': 'Parse server CPU list',
> 'task_duration': 1}
> 2020-06-10 18:25:30,387+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3359942b0> kwargs
> 2020-06-10 18:25:30,897+0200 INFO ansible task start {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_task': 'ovirt.hosted_engine_setup : debug'}
> 2020-06-10 18:25:30,897+0200 DEBUG ansible on_any args TASK:
> ovirt.hosted_engine_setup : debug kwargs is_conditional:False
> 2020-06-10 18:25:30,898+0200 DEBUG ansible on_any args localhostTASK:
> ovirt.hosted_engine_setup : debug kwargs
> 2020-06-10 18:25:31,488+0200 INFO ansible ok {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_host': 'localhost', 'ansible_task': '', 'task_duration': 1}
> 2020-06-10 18:25:31,489+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc335656198> kwargs
> 2020-06-10 18:25:31,996+0200 INFO ansible task start {'status': 'OK',
> 'ansible_type': 'task', 'ansible_playbook':
> '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml',
> 'ansible_task': 'ovirt.hosted_engine_setup : Convert CPU model name'}
> 2020-06-10 18:25:31,996+0200 DEBUG ansible on_any args TASK:
> ovirt.hosted_engine_setup : Convert CPU model name kwargs
> is_conditional:False
> 2020-06-10 18:25:31,997+0200 DEBUG ansible on_any args localhostTASK:
> ovirt.hosted_engine_setup : Convert CPU model name kwargs
> 2020-06-10 18:25:32,500+0200 DEBUG var changed: host "localhost" var
> "ansible_play_hosts" type "<class 'list'>" value: "[]"
> 2020-06-10 18:25:32,500+0200 DEBUG var changed: host "localhost" var
> "ansible_play_batch" type "<class 'list'>" value: "[]"
> 2020-06-10 18:25:32,501+0200 DEBUG var changed: host "localhost" var
> "play_hosts" type "<class 'list'>" value: "[]"
> 2020-06-10 18:25:32,501+0200 ERROR ansible failed {
> "ansible_host": "localhost",
> "ansible_playbook":
> "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
> "ansible_result": {
> "_ansible_no_log": false,
> "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' shorthand syntax and YAML in this task. Only one syntax may be
> used.\n"
> },
> "ansible_task": "Convert CPU model name",
> "ansible_type": "task",
> "status": "FAILED",
> "task_duration": 0
> }
> 2020-06-10 18:25:32,501+0200 DEBUG ansible on_any args
> <ansible.executor.task_result.TaskResult object at 0x7fc3358fc438>
> kwargs ignore_errors:None
> 2020-06-10 18:25:32,504+0200 INFO ansible stats {
> "ansible_playbook":
> "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
> "ansible_playbook_duration": "01:10 Minutes",
> "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok':
> 35, 'failures': 1, 'unreachable': 0, 'changed': 5, 'skipped': 5,
> 'rescued': 0, 'ignored': 0}}",
> "ansible_type": "finish",
> "status": "FAILED"
> }
>
>
> Thanks in advance.
>
>
> Best Regards,
> Ángel González.
>
>
> El 10/6/20 a las 8:10, Yedidyah Bar David escribió:
> > On Tue, Jun 9, 2020 at 10:47 PM Strahil Nikolov via Users
> > <users@ovirt.org> wrote:
> >> Can you put something like this before the 'Parse server cpu list' :
> >>
> >> - name: Debug why parsing fails
> >> debug:
> >> msg:
> >> - "Loop is done over {{
> server_cpu_list.json['values']['system_option_value'][0]['value'].split(';
> ')|list|difference(['']) }}"
> >> - "Actual value of server_cpu_dict before the set_fact is {{
> server_cpu_dict }}"
> >>
> >>
> >> Note: e-mail clients can distort code. Don't copy/paste , but type the
> example from above.
> >>
> >> Best Regards,
> >> Strahil Nikolov
> >>
> >> На 9 юни 2020 г. 19:34:07 GMT+03:00, "Angel R. Gonzalez" <
> angel.gonza...@uam.es> написа:
> >>> Hi all!
> >>>
> >>> I'm deploying a host engine in a host node with a 8x Intel(R) Xeon(R)
> >>> CPU E5410 @ 2.33GHz.
> >>>
> >>> The deploy proccess show the next message
> >>>
> >>>> [INFO]TASK [ovirt.hosted_engine_setup : Convert CPU model name]
> >>>> [ERROR]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'
> >>>> shorthand syntax and YAML in this task. Only one syntax may be
> >>> used.\n"}
> >>>
> >>> The ansible deploy script in his 105 line show:
> >>>
> >>>> - 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
> >>> I don´t know ansible and i don't how to resolve this issue. Any idea?
> > Please check/share /var/log/ovirt-hosted-engine-setup/*. Search there,
> e.g.,
> > for server_cpu_list, server_cpu_dict.
> >
> > Your case seems similar to a few others, discussed recently in this
> thread:
> >
> > [ovirt-users] Issues deploying 4.4 with HE on new EPYC hosts
> >
> > Can you please check it?
> >
> > In particular, what OS are you using? Perhaps CentOS Stream?
> >
> > What is the output of:
> >
> > rpm -q qemu-kvm libvirt
> >
> > ?
> >
> > Thanks and best regards,
> > --
> > Didi
> >
> >
> >
> >
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/users@ovirt.org/message/B5NGXFVGUCOIH2TKA3LQ2HRRZU5TU47C/
>
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbona...@redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
<https://mojo.redhat.com/docs/DOC-1199578>*
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/users@ovirt.org/message/Z73LVXODNHNZV6IO6XYFDAFWDLIRZBYS/
