RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 982445 - It covers the orginal /etc/profile file when configuring AES-NI
Summary: It covers the orginal /etc/profile file when configuring AES-NI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-09 05:11 UTC by wanghui
Modified: 2014-01-21 19:45 UTC (History)
14 users (show)

Fixed In Version: ovirt-node-3.0.0-6.el6
Doc Type: Bug Fix
Doc Text:
Previously when configuring AES-NI, it would cover the original /etc/profile file. It also could not delete the values in /etc/profile when deleting the AES-NI bytes in UI. This has been fixed by setting AES-NI correctly when unset in the TUI and also fixing writing to /etc/profile.
Clone Of:
Environment:
Last Closed: 2014-01-21 19:45:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
original&after configuration profile (1.05 KB, application/x-gzip)
2013-07-09 05:11 UTC, wanghui
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC
oVirt gerrit 16597 0 None None None Never

Description wanghui 2013-07-09 05:11:24 UTC
Created attachment 770779 [details]
original&after configuration profile

Description of problem:
When configuring AES-NI, it will cover the original /etc/profile file. And it can not delete the values in /etc/profile when delete the AES-NI bytes in UI.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.5-20130222.0.auto1716.el6
ovirt-node-3.0.0-2.999.20130708020233git0792892.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Enter Security Page, configure AES-NI Bytes Used with 1000.
2. Check in /etc/profile.
3. Delete the AES-NI bytes in UI.
4. Check in UI and /etc/profile file.

Actual results:
After step2, the original /etc/profile was covered by the configuration of AES-NI instead of append.
After step4, the configuration in UI was deleted but wasn't deleted in /etc/profile.

Expected results:
After step2, the /etc/profile saves the configuration of AES-NI as append at the end of the file.
After step4, it should delete the related configuration in the /etc/profile file too.  

Additional info:

Comment 2 haiyang,dong 2013-07-10 01:44:17 UTC
upstream patch:
http://gerrit.ovirt.org/#/c/16597/

The configuration of AES-NI as append at the end of /etc/profile when setting AES-NI in TUI.
Also fix it as to delete the related configuration in the /etc/profile file when 
unset AES-NI in TUI

Comment 3 Fabian Deutsch 2013-07-19 10:17:35 UTC
Fixed in
http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=commit;h=a749c694

Comment 6 wanghui 2013-10-18 09:17:22 UTC
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6.noarch

Steps to test:
1. Install rhev-hypervisor6-6.5-20131017.0.iso.
2. Enter Security Page, configure AES-NI Bytes Used with 1000.
3. Check in /etc/profile.
4. Delete the AES-NI bytes in UI.
5. Check in UI and /etc/profile file.

Test results:
1. After step3, the /etc/profile saves the configuration of AES-NI as append at the end of the file.
2. After step5, it delete the just the configuration of AES-NI.

The bug is fixed in rhev-hypervisor6-6.5-20131017.0.iso. So change the bug's status from ON_QA to VERIFIED.

Comment 9 Cheryn Tan 2013-11-08 00:33:40 UTC
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 11 errata-xmlrpc 2014-01-21 19:45:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0033.html


Note You need to log in before you can comment on or make changes to this bug.