Bug 1261851
Summary: | Cluster cpu type can't be edited | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | jniederm | ||||
Component: | BLL.Virt | Assignee: | jniederm | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ilanit Stein <istein> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | --- | CC: | bsanford, bugs, jniederm, michal.skrivanek, pkliczew, sbonazzo | ||||
Target Milestone: | ovirt-3.6.2 | Keywords: | FutureFeature, Reopened | ||||
Target Release: | 3.6.2 | Flags: | michal.skrivanek:
ovirt-3.6.z?
rule-engine: planning_ack? ofrenkel: devel_ack+ rule-engine: testing_ack+ |
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: |
Feature: (rather bug-fix)
Setting 'CPU type' in freshly created cluster causes NPE. It was fixed without other functionality changes.
Reason:
Result:
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-02-18 11:17:28 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Verified on rhevm 3.6.0-18 cpu type updated with no problem. No stacktrace on engine.log: [20195bd9] Running command: UpdateVdsGroupCommand internal: false. Entities affected : ID: 00000002-0002-0002-0002-00000000006a Type: VdsGroupsAction group EDIT_CLUSTER_CONFIGURATION with role type ADMIN 2015-11-05 14:47:30,585 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-7) [20195bd9] Correlation ID: 20195bd9, Call Stack: null, Custom Event ID: -1, Message: Host cluster Default was updated by admin@internal Since oVirt 3.6.0 has been released, moving from verified to closed current release. The issue still exists on master and 3.6. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. *** Bug 1288122 has been marked as a duplicate of this bug. *** The new occurence also happens because there was no CPU type set - a brand new Cluster without any host This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. Steps to Reproduce (for 1st re-open): 1. Clear engine installation without hosts 2. Open "Default" cluster edit dialog 3. Untick "Enable Virt Service" 4. Tick "Enable Gluster Service" 4. Click Ok *** Bug 1288116 has been marked as a duplicate of this bug. *** Can you please add some doc-text? This bug has target milestone 3.6.2 and is on modified without a target release. This may be perfectly correct, but please check if the patch fixing this bug is included in ovirt-engine-3.6.2. If it's included, please set target-release to 3.6.2 and move to ON_QA. Thanks. Doc-text added. However attached patches are mere bug-fixes so I doubt it is somehow beneficial. Patches http://gerrit.ovirt.org/50017 and http://gerrit.ovirt.org/46001 are in virt-engine-3.6.2 tag. Verified on rhevm 3.6.2.5-0.1.el6. Followed reproduce steps in comment #8. and in addition set the cpu type to "Intel Conroe Family" No stacktrace was seen on engine.log |
Created attachment 1072079 [details] stack-trace.txt Description of problem: ... probably only if none cpu type is currently set (fresh cpu installation). Version-Release number of selected component (if applicable): 4.0 master, commit 26ae556 How reproducible: 100% Steps to Reproduce: 1. Clear engine installation without hosts 2. Open "Default" cluster edit dialog 3. Set CPU type 4. click ok Actual results: stacktrace in engine log, cpu type not saved Expected results: cpu type saved without errors