| Summary: | mpath errors due to faulty hardware should not cause an Anaconda traceback | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Red Hat Case Diagnostics <case-diagnostics> | ||||
| Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0 | CC: | akozumpl, dwysocha, jzeleny, mganisin, rwilliam | ||||
| Target Milestone: | rc | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | anaconda_trace_hash:5089f27184e677bb6e14af1e4e377919b958bbdc3fc4364d8fde8d9c2e0a55d5 | ||||||
| Fixed In Version: | anaconda-13.21.123-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 10:30:54 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 486655 [details]
File: backtrace
There are a lot of errors at the end of your syslog (just scroll all the way to the bottom of the attached backtrace). This indicates to me either a hardware or driver problem. Any idea which it may be? Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Marking this as a dupe per comment #9. If we need to undupe it, we will. *** This bug has been marked as a duplicate of bug 689965 *** Not sure this should be a dup - see comment #8. Is there a reason you feel unhandled exceptions in the installer are acceptable for RHEL6? Might be a lower priority given the specific hardware but can we improve this in some way to flag storage configuration as a possible issue if this hardware is involved? (In reply to comment #11) > Is there a reason you feel unhandled exceptions in the installer are acceptable > for RHEL6? I did not imply nor state that. This bug was reported against RHEL 6.0 GA. Part of my process for 6.2 planning is to clean up our bug lists. Based on the comments, it seemed like this was *probably* fixed with 6.1. It would be extremely useful to us if someone with access to the system in question could try RHEL 6.1 and see if problem persists. Retest and reopen if the problem persists. The bz this got duped to was one where there was no fixed involved, and the resolution was marked as NOTABUG. Indeed this was filed against 6.0, so perhaps there were other fixes that would indeed take care of this, but the bz this got dup'ed to did not show that. Perhaps there's some other bz / fix in the changelog that would apply as a better dup for this bz? I can look to check if we have the hardware to setup a reproducer. Either way, this should be closed, see comment 3 and comment 5. We could argue that there should be no unhandled exceptions occuring, in that case I am going to fix this by checking the return value of 'multipath' and stopping the installer right then. "I am going to fix this by checking the return value of 'multipath' and stopping the installer right then." That sounds like a good fix, re-opening. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Patch is awaiting review at: https://www.redhat.com/archives/anaconda-devel-list/2011-June/msg00129.html A revised patch has been sent for a review: https://www.redhat.com/archives/anaconda-devel-list/2011-June/msg00224.html Fixed by 1b6af96a2639765b6d0ea5fa5ff5f98d25f8d23b on rhel6-branch and 422194357976b0f4e4b7d3c02615a6628bd7617a on master. 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-2011-1565.html |
The following was filed automatically by anaconda: anaconda 13.21.82 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 3204, in setupPartitions self.name) File "/usr/lib/anaconda/storage/devices.py", line 3268, in setup self.setupPartitions() File "/usr/lib/anaconda/storage/devicetree.py", line 2052, in populate mp.setup() File "/usr/lib/anaconda/storage/__init__.py", line 385, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize storage.reset() File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1338, in nextClicked self.anaconda.dispatch.gotoNext() MPathError: multipath partition activation failed for 'mpatha'