Bug 1112180
| Summary: | Error occur when change the AES-NI setting before after rhevh upgrade | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | wanghui <huiwa> | ||||
| Component: | ovirt-node | Assignee: | Douglas Schilling Landgraf <dougsland> | ||||
| Status: | CLOSED EOL | QA Contact: | wanghui <huiwa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | cshao, dfediuck, fdeutsch, gklein, gouyang, leiwang, yaniwang, ycui | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | node | ||||||
| Fixed In Version: | ovirt-node-3.3.0-0.4.20150906git14a6024.el7ev | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-28 09:32:07 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: |
|
||||||
It could be that the file was not persisted when sed was run on it. Hi, This report is targeted to 3.6 version which will be based only in EL7.1. I cannot reproduce the report using the below scenarios. - Setup 1000 bytes into AES-NI via TUI - Upgrade from rhev-hypervisor7-7.0-20150127.0 to rhev-hypervisor7-7.1-20150609.0 - Reboot - Everything ok - Setup 1000 bytes into AES-NI via TUI - Upgrade from rhev-hypervisor7-7.1-20150603.0.iso to rhev-hypervisor7-7.1-20150609.0 - Reboot - Everything ok - Setup 1000 bytes into AES-NI via TUI - Upgrade from rhev-hypervisor7-7.1-20150609.0 to rhev-hypervisor7-7.1-20150609.0 - Reboot - Everything ok Moving to ON_QA for double check. Test version: rhev-hypervisor7-7.2-20151025.0.el7ev ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch Test steps: 1. Install rhev-hypervisor7-7.0-20150127.0 2. Setup 1000 bytes into AES-NI via TUI 3. Upgrade from rhev-hypervisor7-7.0-20150127.0 to rhev-hypervisor7-7.2-20151025.0.el7ev 4. Reboot 5. Disable AES-NI 6. Enable SSH password authentication Test result: 1. After step5, AES-NI can be disabled. 2. After step6, SSH password authentication can be enabled. This issue is el6 only. So it can not be reproduced in rhev3.6 for el7. Thus is can not be verified in rhev3.6. I will close this issue with EOL now. |
Created attachment 911369 [details] aes_ni error Description of problem: It report an error when applying disable in AES-NI settings after upgrade while it is enabled before upgrading. And this issue also happend when you just change the ssh password authentication. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20140618.0.el6ev ovirt-node-3.0.1-18.el6_5.10.noarch How reproducible: 100% Steps to Reproduce: Scenario 1: 1. Install rhev-hypervisor6-6.5-20140603.2.el6ev. 2. Enabled AES-NI in TUI by setting bytes as 1000. 3. Upgrade to rhev-hypervisor6-6.5-20140618.0.el6ev by cmdline. 4. Disabled AES-NI in TUI. Scenario 2: 1. Install rhev-hypervisor6-6.5-20140603.2.el6ev. 2. Enable AES-NI in TUI by setting bytes as 1000. 3. Upgrade to rhev-hypervisor6-6.5-20140618.0.el6ev by cmdline. 4. Enabled SSH password authentication in TUI. Actual results: 1. It will report error as follows in step4 as aes_ni.png Expected results: 1. It should not report error in step4. Additional info: