Bug 696907

Summary:	Anaconda creates mdadm.conf when not needed
Product:	Red Hat Enterprise Linux 6	Reporter:	Alexander Todorov <atodorov>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	clumens, notting, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-13.21.113-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	696110	Environment:
Last Closed:	2011-05-19 12:40:28 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:	670159

Description Alexander Todorov 2011-04-15 08:43:34 UTC

+++ This bug was initially created as a clone of Bug #696110 +++

Created attachment 491696 [details]
boot.log

Description of problem:

Starting RPC idmapd:                                       [  OK  ]
/etc/rc3.d/S25netfs: line 47: mdadm: command not found
Setting up Logical Volume Management:   2 logical volume(s) in volume group "vg_dhcp70188" now active

This is when booting a KVM domU of the latest Workstation variant (snap #3) which has 2 iSCSI targets acting as PVs. 

Version-Release number of selected component (if applicable):
initscripts-9.03.22-1.el6.x86_64
anaconda version 13.21.111

How reproducible:


Steps to Reproduce:
1. Configure tgtd to export 2 iSCSI targets
2. Start KVM domU install with a local disk and attach to the 2 targets
3. Select to use all space on all disks (will create LVM)
4. Select minimal package set

Actual results:
mdadm not found because it is not installed.

Expected results:
If mdadm is necessary I suppose it should have been installed automatically by anaconda.

Additional info:


.... SKIP ....


--- Additional comment from clumens on 2011-04-15 05:32:14 EEST ---

(In reply to comment #12)
> Chris - do we want anaconda writing out mdadm.conf if mdadm isn't being
> installed?

We should create /etc/mdadm.conf on the basis of RAID devices being created.  If there are none, the file should not be created.

Comment 1 Alexander Todorov 2011-04-15 08:44:18 UTC

Filing here for anaconda. 

Expected result:
No /etc/mdadm.conf if no RAID devices are created during install.

Comment 2 Chris Lumens 2011-04-15 15:26:11 UTC

https://www.redhat.com/archives/anaconda-devel-list/2011-April/msg00165.html

Comment 3 RHEL Program Management 2011-04-15 19:39:29 UTC

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.

Comment 6 Alexander Todorov 2011-04-20 13:14:46 UTC

Easier steps to reproduce:

1) Perform install on local disk using autopart and minimal package set
2) No RAID arrays will be created but anaconda will create non-empty /etc/mdadm.conf


Tested with anaconda-13.21.114-1 from 0420.n.0 nightly - mdadm.conf was not created.

Comment 7 errata-xmlrpc 2011-05-19 12:40:28 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0530.html