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 982425 - The transaction page also shown info "(2/2) configuring SSH AES NI" when only configuring ssh password authentication.
Summary: The transaction page also shown info "(2/2) configuring SSH AES NI" when only...
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: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-09 02:12 UTC by haiyang,dong
Modified: 2014-01-21 19:45 UTC (History)
14 users (show)

Fixed In Version: ovirt-node-3.0.1-2.el6
Doc Type: Bug Fix
Doc Text:
Incorrect information was being shown when performing transactions on the security page, for example, performing "Enable SSH password authentication" also showed "(2/2) configuring SSH AES NI" when this wasn't performed. Previously the transaction elements appearing in the transactions used on the security page weren't connected to the changes done in the TUI. Now the same transaction elements are used in the transaction which has eliminated these errors.
Clone Of:
Environment:
Last Closed: 2014-01-21 19:45:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
attached Screenshot for "transaction of security page" (5.61 KB, image/png)
2013-07-09 02:12 UTC, haiyang,dong 		no flags Details
View All


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 19359 0 None None None Never

Description haiyang,dong 2013-07-09 02:12:18 UTC 
Created attachment 770745 [details]
attached Screenshot for "transaction of security page"

Description of problem:
Enter Security page and select "Enable SSH password authentication [].
then click "Save" button to apply it.
But The transaction page also shown info "(2/2) configuring SSH AES NI" when only configuring ssh password authentication. (Seen transaction for security page.png) 

Also the same issue when only configuring "SSH AES NI", the transaction page also shown info
"(1/2) Configuring SSH password authentication"

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 and select "Enable SSH password authentication [].
2.click "Save" button to apply it.

Actual result:
After step 2, the transaction page also shown info "(2/2) configuring SSH AES NI" when only configuring ssh password authentication.                                                     

Expect result:
After step 2, the transaction page should didn't show info "(2/2) configuring SSH AES NI" when only configuring ssh password authentication.    

Additional info:
Comment 2 Fabian Deutsch 2013-09-18 10:44:29 UTC 
As the commit message says: We are not trying to identify the transaction items which need to be run anymore, instead we are running all transaction items (the transaction items are displayed on the screen).
Running all items every time will give a consistent experience to the user.
Comment 5 haiyang,dong 2013-10-21 11:22:51 UTC 
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6

Same comment 2 Description,when only configuring ssh password authentication/ssh strong RNG or ssh AES NI, the transaction page will show all transaction items:
(1/3) Configuring SSH password authentication
(2/3) Configuring SSH strong RNG
(3/3) Configuring SSH AES NI

this bug has been fixed, change the status into "VERIFIED"
Comment 8 Cheryn Tan 2013-11-08 00:37:52 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 10 errata-xmlrpc 2014-01-21 19:45:13 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.