Description of problem: When trying to add cluster cpu-architecture provided in error message is not correct. Version-Release number of selected component (if applicable): ovirt-rc1 How reproducible: 100% Steps to Reproduce: [oVirt shell (connected)]# add cluster --name "foo" --data_center-name Default --cpu-architecture ppc64 ==================================== ERROR ================================= status: 400 reason: Bad Request detail: ppc64 is not a member of Architecture. Possible values for Architecture are: undefined, x86_64, ppc64 ============================================================================ [oVirt shell (connected)]# add cluster --name "foo" --data_center-name Default --cpu-architecture x86_64 ==================================== ERROR ================================= status: 400 reason: Bad Request detail: x86_64 is not a member of Architecture. Possible values for Architecture are: undefined, x86_64, ppc64 ============================================================================ [oVirt shell (connected)]# add cluster --name "foo" --data_center-name Default --cpu-architecture undefined ==================================== ERROR ================================= status: 400 reason: Bad Request detail: undefined is not a member of Architecture. Possible values for Architecture are: undefined, x86_64, ppc64 ============================================================================ Actual results: Any of possible valuas are impossible. Expected results: Possible values should be possible to add. Additional info: Nothing in engine log as the action ends with error.
The problem is that we are performing the lookup of the architecture using a case sensitive search, but the names of the architectures inside the engine are upper case. The proposed fix is to change the comparison to ignore case. Note that in order to add a cluster you also need to specify the type of CPU: # add cluster --name foo --data_center-name Default --cpu-architecture x86_64 --cpu-id "Intel SandyBridge Family"
ok, ovirt-engine-backend-3.5.0-0.0.master.20140911085455.gite1c5ffd.el6.noarch
oVirt 3.5 has been released and should include the fix for this issue.