# AWX-Operator 0.30.0 failed

**URL:** <https://forum.ansible.com/t/awx-operator-0-30-0-failed/37178>\
**Category:** AWX Project\
**Tags:** awx-project, awx\
**Created:** [October 5, 2022, 5:50am UTC](https://forum.ansible.com/t/awx-operator-0-30-0-failed/37178 "2022-10-05T05:50:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrea\_Lenarduzzi](https://avatars.discourse-cdn.com/v4/letter/a/c77e96/32.png) [@Andrea\_Lenarduzzi](https://forum.ansible.com/u/Andrea_Lenarduzzi)\
**Post date:** [October 5, 2022, 5:50am UTC](https://forum.ansible.com/t/awx-operator-0-30-0-failed/37178/1 "2022-10-05T05:50:01Z")

</div>

Debian 11 on Proxmox vm

k3s v1.24.6+k3s1

Operator 0.30.0

`kubectl logs awx-web ---->`Fatal glibc error: CPU does not support x86-64-v2

kubectl logs awx-task ----\>Fatal glibc error: CPU does not support x86-64-v2

How can I fix it?  
Thank you  
Regards

---

<div class="post-metadata">

**Author:** ![kurokobo1](https://avatars.discourse-cdn.com/v4/letter/k/f0a364/32.png) [@kurokobo1](https://forum.ansible.com/u/kurokobo1)\
**Post date:** [October 5, 2022, 5:57am UTC](https://forum.ansible.com/t/awx-operator-0-30-0-failed/37178/2 "2022-10-05T05:57:32Z")

</div>

Hi,

> Debian 11 on Proxmox vm

Proxmox sometimes causes this issue.  
Try tweaking CPU type for your VM to “Host” instead of default one.

Refer: [https://github.com/ansible/awx/issues/11879](https://github.com/ansible/awx/issues/11879)

---

<div class="post-metadata">

**Author:** ![Andrea\_Lenarduzzi](https://avatars.discourse-cdn.com/v4/letter/a/c77e96/32.png) [@Andrea\_Lenarduzzi](https://forum.ansible.com/u/Andrea_Lenarduzzi)\
**Post date:** [October 5, 2022, 6:02am UTC](https://forum.ansible.com/t/awx-operator-0-30-0-failed/37178/3 "2022-10-05T06:02:24Z")

</div>

Hi, I’ve changed to “Host” —\> same problem  
I’ve to reinstall os?