Bug 696110

Summary: /etc/rc3.d/S25netfs: line 47: mdadm: command not found
Product: Red Hat Enterprise Linux 6 Reporter: Alexander Todorov <atodorov>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: notting, plautrba, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: initscripts-9.03.23-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 696907 (view as bug list) Environment:
Last Closed: 2011-05-19 13:52:08 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    
Attachments:
Description Flags
boot.log
none
anaconda.ifcfg.log
none
anaconda.log
none
program.log
none
storage.log
none
syslog none

Description Alexander Todorov 2011-04-13 09:55:15 UTC
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:

Comment 1 Alexander Todorov 2011-04-13 09:55:50 UTC
Created attachment 491698 [details]
anaconda.ifcfg.log

Comment 2 Alexander Todorov 2011-04-13 09:55:59 UTC
Created attachment 491699 [details]
anaconda.log

Comment 3 Alexander Todorov 2011-04-13 09:56:08 UTC
Created attachment 491700 [details]
program.log

Comment 4 Alexander Todorov 2011-04-13 09:56:16 UTC
Created attachment 491701 [details]
storage.log

Comment 5 Alexander Todorov 2011-04-13 09:56:23 UTC
Created attachment 491702 [details]
syslog

Comment 6 Alexander Todorov 2011-04-13 10:33:47 UTC
Happens also with 0412.n.0 Server/Workstation.

Comment 7 Chris Lumens 2011-04-13 13:17:10 UTC
If you didn't do any RAID partitioning setup, you didn't need mdadm to activate anything therefore it was not marked for installation.  If something's changed in initscripts that make mdadm required for all installs now, that is either a bug in initscripts or comps needs to be changed to make mdadm required.

Comment 8 Bill Nottingham 2011-04-13 13:39:10 UTC
Need ae1353b8528561a41fe82314f3ee010a82e6da7a backported.

Comment 9 Bill Nottingham 2011-04-13 13:40:12 UTC
Out of curiousity - what's your mdadm.conf look like?

Comment 11 Alexander Todorov 2011-04-14 12:03:42 UTC
(In reply to comment #9)
> Out of curiousity - what's your mdadm.conf look like?

# cat /etc/mdadm.conf 
# mdadm.conf written out by anaconda
MAILADDR root
AUTO +imsm +1.x -all

Comment 12 Bill Nottingham 2011-04-14 14:14:54 UTC
Chris - do we want anaconda writing out mdadm.conf if mdadm isn't being installed?

Comment 14 Chris Lumens 2011-04-15 02:32:14 UTC
(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 18 errata-xmlrpc 2011-05-19 13:52:08 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-0647.html