Red Hat Bugzilla – Bug 911835
Automated Installation parameters miss "AES-NI" and "NFSv4"
Last modified: 2014-01-21 14:26:42 EST
Description of problem: AES-NI and NFSv4 can show on TUI in RHEV-H, but miss in automated Installation parameters. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130214.0.el6 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: AES-NI and NFSv4 can show on TUI in RHEV-H, but miss in automated Installation parameters. Expected results: "AES-NI" and "NFSv4" are included in automated installation parameters. Additional info:
Test version: rhevh-6.5-20131024.1.0.iso ovirt-node-3.0.1-6.el6.noarch Auto with below parameters can successfully. BOOTIF=em1 storage_init=/dev/sda nfsv4_domain=domainname disable_aes_ni=y firstboot "AES-NI" and "NFSv4" are included in automated installation parameters. So the bug is fixed, change bug status to VERIFIED.
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.
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