[ovirt-users] Re: The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.

2019-06-14 Thread Strahil
In the docs, the proper order to update is:
1. update ovirt-setup packages on the engine
yum update ovirt\*setup\*
2. update the engine
engine-setup
3. update the OS on the engine
yum update
4. reboot the engine if kernel/glibc/systemd got updated
5 upgrade hosts 1 by 1

Best Regards,
Strahil NikolovOn Jun 13, 2019 16:27, sandeepkumar...@gmail.com wrote:
>
> Thank you. 
>
> I upgraded all three hosts one by one to oVirt-4.3 and then HE. After the 
> upgrade, I was able to change the CPU Type. 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/NGUEEF4DVLBXLUOHMSS2AYK6FE45VSXM/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AZDBCK475LJ67MDCDTCBREM45LBN4HBR/


[ovirt-users] Re: The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.

2019-06-13 Thread sandeepkumar86k
Thank you.

I upgraded all three hosts one by one to oVirt-4.3 and then HE. After the 
upgrade, I was able to change the CPU Type.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NGUEEF4DVLBXLUOHMSS2AYK6FE45VSXM/


[ovirt-users] Re: The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.

2019-06-10 Thread Juhani Rautiainen
Hi!

Epyc is not available in oVirt-4.2. If you can recover the system and
can upgrade to oVirt-4.3 it then you can switch to Epyc (I have system
with Epyc's running in 4.3). For recovery I would try to roll back
changes you did to database.

-Juhani


-Juhani

On Mon, Jun 10, 2019 at 11:46 AM  wrote:
>
> Hi,
>
> I am having trouble in fixing the CPU type of my oVirt cluster.
>
> I have AMD EPYC 7551P 32-Core Processor hosts(x3) in a gluster cluster. The 
> HE and cluster by default had the: AMD Opteron 23xx (Gen 3 Class Opteron).
>
> I tried changing it with this 
> method(https://lists.ovirt.org/archives/list/users@ovirt.org/thread/XYY2WAGWXBL5YA6KAQY3ZEBVFOKELAKE/),
> it didn't work as I can't move the Host to another cluster it complains 
> (Error while executing action: ***:Cannot edit Host. Server having 
> Gluster volume.)
>
> Then I tried updating the cpu_name manually in DB by following: 
> https://www.mail-archive.com/users@ovirt.org/msg33177.html
> After the Update, the web UI shows it changed to AMD EPYC but if I click on 
> Edit cluster it shows the "Intel Conroe Family" and again doesn't allow to 
> modify.
>
> I am now stuck with unusable oVirt setup, my existing VMs won't start and 
> throw: Error while executing action: **: The CPU type of the cluster is 
> unknown. Its possible to change the cluster cpu or set a different one per 
> VM.)
>
> Please help or suggest to fix this issue.
>
> HE:
> cat /proc/cpuinfo |grep "model name"
> model name  : AMD Opteron 23xx (Gen 3 Class Opteron)
> model name  : AMD Opteron 23xx (Gen 3 Class Opteron)
> model name  : AMD Opteron 23xx (Gen 3 Class Opteron)
> model name  : AMD Opteron 23xx (Gen 3 Class Opteron)
>
> rpm -qa |grep -i ovirt
> ovirt-ansible-image-template-1.1.9-1.el7.noarch
> ovirt-engine-dwh-setup-4.2.4.3-1.el7.noarch
> ovirt-engine-backend-4.2.8.2-1.el7.noarch
> ovirt-engine-extension-aaa-ldap-1.3.8-1.el7.noarch
> ovirt-engine-extension-aaa-jdbc-1.1.7-1.el7.centos.noarch
> ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
> ovirt-ansible-hosted-engine-setup-1.0.2-1.el7.noarch
> ovirt-host-deploy-java-1.7.4-1.el7.noarch
> ovirt-engine-setup-plugin-websocket-proxy-4.2.8.2-1.el7.noarch
> ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.2.8.2-1.el7.noarch
> ovirt-ansible-engine-setup-1.1.6-1.el7.noarch
> ovirt-ansible-cluster-upgrade-1.1.10-1.el7.noarch
> ovirt-ansible-roles-1.1.6-1.el7.noarch
> ovirt-release42-4.2.8-1.el7.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-4.2.8.2-1.el7.noarch
> ovirt-engine-tools-backup-4.2.8.2-1.el7.noarch
> ovirt-provider-ovn-1.2.18-1.el7.noarch
> ovirt-imageio-common-1.4.6-1.el7.x86_64
> ovirt-js-dependencies-1.2.0-3.1.el7.centos.noarch
> ovirt-cockpit-sso-0.0.4-1.el7.noarch
> ovirt-engine-restapi-4.2.8.2-1.el7.noarch
> ovirt-engine-vmconsole-proxy-helper-4.2.8.2-1.el7.noarch
> ovirt-engine-api-explorer-0.0.2-1.el7.centos.noarch
> ovirt-engine-lib-4.2.8.2-1.el7.noarch
> ovirt-engine-setup-base-4.2.8.2-1.el7.noarch
> ovirt-engine-metrics-1.1.8.1-1.el7.noarch
> ovirt-ansible-repositories-1.1.3-1.el7.noarch
> ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
> ovirt-ansible-infra-1.1.10-1.el7.noarch
> ovirt-ansible-shutdown-env-1.0.0-1.el7.noarch
> ovirt-engine-dwh-4.2.4.3-1.el7.noarch
> ovirt-iso-uploader-4.2.0-1.el7.centos.noarch
> ovirt-engine-webadmin-portal-4.2.8.2-1.el7.noarch
> ovirt-engine-dbscripts-4.2.8.2-1.el7.noarch
> ovirt-engine-setup-plugin-ovirt-engine-4.2.8.2-1.el7.noarch
> ovirt-engine-extension-aaa-ldap-setup-1.3.8-1.el7.noarch
> ovirt-engine-extensions-api-impl-4.2.8.2-1.el7.noarch
> ovirt-host-deploy-1.7.4-1.el7.noarch
> ovirt-vmconsole-1.0.6-2.el7.noarch
> python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64
> ovirt-engine-wildfly-14.0.1-3.el7.x86_64
> ovirt-guest-agent-common-1.0.16-1.el7.noarch
> ovirt-ansible-v2v-conversion-host-1.9.0-1.el7.noarch
> ovirt-ansible-manageiq-1.1.13-1.el7.noarch
> ovirt-setup-lib-1.1.5-1.el7.noarch
> ovirt-engine-websocket-proxy-4.2.8.2-1.el7.noarch
> ovirt-engine-dashboard-1.2.4-1.el7.noarch
> ovirt-engine-setup-4.2.8.2-1.el7.noarch
> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
> ovirt-web-ui-1.4.5-1.el7.noarch
> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
> ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
> ovirt-imageio-proxy-1.4.6-1.el7.noarch
> ovirt-engine-tools-4.2.8.2-1.el7.noarch
> ovirt-engine-4.2.8.2-1.el7.noarch
> ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch
>
> 3xHosts:
> cat /proc/cpuinfo |grep "model name"
> model name  : AMD EPYC 7551P 32-Core Processor
> model name  : AMD EPYC 7551P 32-Core Processor
> model name  : AMD EPYC 7551P 32-Core Processor
>
> rpm -qa |grep -i ovirt
> ovirt-release42-4.2.8-1.el7.noarch
> cockpit-ovirt-dashboard-0.11.38-1.el7.noarch
> ovirt-vmconsole-1.0.6-2.el7.noarch
> python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64
> cockpit-machines-ovirt-193-2.el7.noarch
> ovirt-imageio-daemon-1.4.6-1.el7.noarch
> ovirt-hosted-engine-setup-2.2.33-1.el7.noa