Bug 972319

Summary: [RFE]"Bytes Used" shouldn't be edited after disabled "AES-NI"
Product: [Retired] oVirt Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: haiyang,dong <hadong>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acathrow, bsarathy, cshao, fdeutsch, gouyang, hadong, jboggs, leiwang, mgoldboi, ovirt-bugs, ovirt-maint, ycui
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.4.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 907806 Environment:
Last Closed: 2014-04-24 16:07:30 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:
Bug Depends On: 907806, 911398    
Bug Blocks:    

Description haiyang,dong 2013-06-08 11:40:14 UTC
+++ This bug was initially created as a clone of Bug #907806 +++

Description of problem:
Clean install rhev-hypervisor6-6.4-20130130.0.2.el6,
Enter into Security Page, Disabled "AES-NI", but the label of "Bytes Used" still can be edited,
but "Bytes Used" shouldn't be edited after disabled "AES-NI".

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130130.0.2.el6

How reproducible:
100%

Steps to Reproduce:
1.Clean install rhev-hypervisor6-6.4-20130130.0.2.el6
2.Enter into Security Page, Disabled "AES-NI"

Actual results:
After disabled "AES-NI",the label of "Bytes Used" still can be edited

Expected results:
"Bytes Used" shouldn't be edited after disabled "AES-NI"

Additional info:

--- Additional comment from RHEL Product and Program Management on 2013-02-05 05:31:02 EST ---

Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Ludek Smid on 2013-03-07 13:37:46 EST ---

Since the release flag was set to ? after the qa_ack flag was set to + (was likely set for the previous release), the qa_ack flag has been reset to ? by the bugbot (pm-rhel). This action ensures the proper review by Product Management.

Comment 1 haiyang,dong 2013-06-08 11:47:21 UTC
This issue can be reproduced on ovirt-node upstream build:
ovirt-node-iso-3.0.0-0.999.999.20130603183100git6c4298c.811.fc18.iso

Comment 2 haiyang,dong 2013-06-13 01:35:10 UTC
This is resolved in: 
http://gerrit.ovirt.org/#/c/15446/