Just to chime in here, trying a fresh hosted engine deploy today on AMD EPYC
servers, the exact same error kills the deploy. So it's not you or your
CPUs/servers, there's a bug in the Ansible routine that was introduced with
4.4.2 that makes hosted engine deployment impossible.
I was able to d
Thanks again for the help on this.
Summary: Got past one roadblock only to hit another.
Time to give up.
Feel free to review my notes in case I missed anything.
I had to give myself a bit of crash course in Ansible to follow the
playbook.
See if I have this correct:
~~~
100 - name: Par
It seems that this one fails :
- name: Parse server CPU list
set_fact:
server_cpu_dict: "{{ server_cpu_dict |
combine({item.split(':')[1]: item.split(':')[3]}) }}"
In cases like that I usually define a new variable.
Can you put another task before that like:
- name: Debug server_cpu_
In my previous reply:
>> Ansible task reports them as Xeon 5130.
>> According to Intel Ark these fall in the Woodcrest family, which is
>> older the Nehalem.
Xeon 5130 "Woodcrest"
Do you need something more specific or different?
I also found one a reply from you on an older thread and added it
You didn't mention your CPU type.
Best Regards,
Strahil Nikolov
В сряда, 16 септември 2020 г., 20:44:23 Гринуич+3, Michael Blanton
написа:
Wondering if there are any suggestions here before I wipe these nodes
and go back to another Hypervisor.
On 9/14/2020 12:59 PM, Michael Blan
Wondering if there are any suggestions here before I wipe these nodes
and go back to another Hypervisor.
On 9/14/2020 12:59 PM, Michael Blanton wrote:
Thanks for the quick response.
Ansible task reports them as Xeon 5130.
According to Intel Ark these fall in the Woodcrest family, which is
Thanks for the quick response.
Ansible task reports them as Xeon 5130.
According to Intel Ark these fall in the Woodcrest family, which is
older the Nehalem.
Obviously the CPUs support virtualization.
I also confirmed the required extensions from the oVirt documents.
# grep -E 'svm|vmx' /proc
What is the CPU? I'm asking because you said it was old servers, and at
some point oVirt started filtering out old CPU types which were no longer
supported under windows. There was also the case where if a certain bios
option wasn't enabled (AES?) a westmere(supported) reported as an older
model
8 matches
Mail list logo
