Bug 1142658

Summary:	[ppc64] Cannot create Cluster. This resilience policy is not supported in this CPU architecture.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	ovirt-engine	Assignee:	Vitor de Lima <vdelima>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	ecohen, gklein, iheim, lpeer, mavital, michal.skrivanek, nyechiel, ofrenkel, rbalakri, Rhev-m-bugs, vdelima, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	ppc64
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	vt9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 08:28:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Belka 2014-09-17 07:35:34 UTC

Description of problem:

[oVirt shell (connected)]# add cluster --name power_foo --data_center-name Default --cpu-architecture ppc64 --cpu-id "IBM POWER 8"                                            
  =================================================================================== ERROR ================================================================================
  status: 409
  reason: Conflict
  detail: Cannot create Cluster. This resilience policy is not supported in this CPU architecture.
  ==========================================================================================================================================================================

Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.5.0-0.0.master.20140911085455.gite1c5ffd.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. create ppc64 cluster
2.
3.

Actual results:
failure

Expected results:
should work

Additional info:
works on d/s rhevm-backend-3.5.0-0.12.beta.el6ev.noarch

Comment 1 Jiri Belka 2014-09-17 07:41:24 UTC

strange, it sometimes works in UI - Admin Portal- but not in {ovirt,rhevm}-cli.

* works:
  - Cluster  main tab, define CPU arch, CPU type, name and click OK

* doesn't work:
  - Data Centers main tab, Guide Me, Add another Cluster, fill above data

Comment 2 Jiri Belka 2014-09-17 07:43:40 UTC

[RHEVM shell (connected)]# add cluster --name power_foo --data_center-name Default --cpu-architecture ppc64 --cpu-id "IBM POWER 8"
  =================================================================================== ERROR ================================================================================
  status: 409
  reason: Conflict
  detail: Cannot create Cluster. This resilience policy is not supported in this CPU architecture.
  ==========================================================================================================================================================================

[RHEVM shell (connected)]# 

  ==========================================================================================================================================================================
                                                                    >>> disconnected from RHEVM manager <<<
  ==========================================================================================================================================================================

[root@jb-rhevm35 ~]# rpm -q rhevm-backend rhevm-cli
rhevm-backend-3.5.0-0.12.beta.el6ev.noarch
rhevm-cli-3.5.0.4-1.el6ev.noarch

Comment 3 Jiri Belka 2014-09-17 07:44:58 UTC

Steps to Reproduce:
1. create ppc64 cluster either via cli or from 'Data Centers' maintab and 'Guide Me'/Add another Cluster dialog
2.
3.

Comment 4 Omer Frenkel 2014-09-18 14:40:06 UTC

The problem is that the default policy is migrate on error, which is currently not supported for ppc, so if user doesnt select policy, the default is used.

not sure if this limitation is still relevant, assuming migration is supported on ppc now

Comment 5 Vitor de Lima 2014-09-19 13:36:36 UTC

This bug should be fixed by changes 21523 and 25048 (which was abandoned).

Comment 6 Omer Frenkel 2014-09-21 12:33:05 UTC

we should undo changes 21523 and remove the specific code that blocks migration for ppc, as it should be supported

Comment 7 Vitor de Lima 2014-09-22 16:09:16 UTC

It still is not supported in the lastest stable QEMU, the remaining patches to enable it were posted but they are still pending review from the community.

Comment 8 Michal Skrivanek 2014-10-23 10:14:22 UTC

IIUC the changes are 3.5+ only?

Comment 9 Vitor de Lima 2014-10-23 11:33:39 UTC

Yes, this problem does not happen in 3.4.

Comment 10 Lukas Svaty 2014-12-22 11:31:03 UTC

verified in vt13.4

Comment 11 Omer Frenkel 2015-02-17 08:28:48 UTC

RHEV-M 3.5.0 has been released