Bug 916498
Summary: | [RFE]red screen observed while clicking on "Flash Lights to Identify" button. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | haiyang,dong <hadong> |
Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.4 | CC: | acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, jboggs, leiwang, lnovich, mburns, ovirt-maint, ycui |
Target Milestone: | rc | Keywords: | FutureFeature, TestOnly |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
A red screen was observed while clicking on the "Flash Lights to Identify" button in the 'network detail page'. The system now operates correctly and ends up on a setting process page.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-21 19:27:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 911398 |
Description
haiyang,dong
2013-02-28 07:46:44 UTC
Pretty sure this is not an issue with the new UI. Can you test when we provide initial builds of 6.5? Test version: rhev-hypervisor6-6.5-20130725.0.el6 ovirt-node-3.0.0-6.1.el6 Tested as follows: 1. Clean install rhev-hypervisor6-6.5-20130725.0.el6 2. Enter network detail page. 3. Clicking on "Flash Lights to Identify" button After step3, that nic will be flashed lights for ten times, and then prompt notice screen to user. Red screen wasn't observed during the above steps so this bug has been fixed, change the status into "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 |