Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1100944

Summary: An error occurred when configuring ssh strong RHG
Product: [Retired] oVirt Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: cshao, gklein, gouyang, hadong, huiwa, jboggs, leiwang, mgoldboi, oourfali, ovirt-bugs, ovirt-maint, rbalakri, ycui, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:35:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
attached Screenshot none

Description haiyang,dong 2014-05-24 06:48:33 UTC 
Created attachment 898858 [details]
attached Screenshot

Description of problem:
An error occured while configuring ssh strong RHG.
Command 'sed -ic '/OPENSSL_DISABLE_AES_NI/d' /etc/profile' returned
non-zero exit status 4(Seen an error occurred in security configuration.png)

Version-Release number of selected component (if applicable):
In the master branch of ovirt-node upstream
recipe: ql2500 is only available in RHEL
Change-Id: Ie853a66749c9fca9a649f89e55c4d5bd61edd156

How reproducible:
100%



Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 haiyang,dong 2014-05-24 06:51:47 UTC 
No this issue in downstream git, after diff them , check that due to miss to unmount_config "/etc/profile" before edit it in upstream master branch.
so add a patch into upstsream
http://gerrit.ovirt.org/#/c/28074/
Comment 2 Sandro Bonazzola 2014-10-17 12:35:45 UTC 
oVirt 3.5 has been released and should include the fix for this issue.