Bug 207544
Summary: | mkinitrd fails to add lvm components when clustering is enabled. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Sandeep K. Shandilya <sandeep_k_shandilya> |
Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | jlaska, kanderso, rkenna, wwlinuxengineering |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | mkinitrd-5.1.19-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-26 11:49:41 UTC | Type: | --- |
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: | 200812 |
Description
Sandeep K. Shandilya
2006-09-21 15:40:22 UTC
Could you include the steps you used to enable clustering here? We don't do that in the installer, so there's some step you've left out, and I want to make sure I'm addressing the correct scenario. (In reply to comment #1) > Could you include the steps you used to enable clustering here? We don't do > that in the installer, so there's some step you've left out, and I want to make > sure I'm addressing the correct scenario. Hello Clustering is not enabled on system as yet but the lvm.conf file has the line locking_type=2 and all commands like vgscan abort with the message Connect() failed on local socket: Connection refused Locking type 2 Initialisation failed If I edit lvm.conf and change locking_type=1 then everything works fine and the initrd is correctly built. (In reply to comment #2) > (In reply to comment #1) > > Could you include the steps you used to enable clustering here? We don't do > > that in the installer, so there's some step you've left out, and I want to make > > sure I'm addressing the correct scenario. > Hello > > Clustering is not enabled on system as yet(selected for install by > using the install key VCS)but the lvm.conf file has the line > locking_type=2 and all commands like vgscan abort with the message > Connect() failed on local socket: Connection refused > Locking type 2 Initialisation failed > If I edit lvm.conf and change locking_type=1 then everything works fine and the > initrd is correctly built. We don't install with locking_type=2 . How is it getting set to that value? (In reply to comment #4) > We don't install with locking_type=2 . How is it getting set to that value? During installation there is a prompt for the serial no, I enter VCS (means I choose Virutalisation, Clustering and and Advanced Storage) and I see that locking type is set to 2 in lvm.conf. That may be the real issue. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering. This request is not yet committed for inclusion in release. Can you please try this with a more recent tree than beta1, and report if it's still a problem? (In reply to comment #10) > Can you please try this with a more recent tree than beta1, and report if it's > still a problem? tried with the latest weekly build with mkinitrd version 5.1.19-1. lvm2 or lvm2-clustering version 2.02.10-1.0.RHEL5 The issue does not occur. This has been fixed. |