Bug 956026

Summary:	If rebuild of IMSM RAID5 volume is started in OROM, it does not proceed in OS.
Product:	[Fedora] Fedora	Reporter:	Jes Sorensen <Jes.Sorensen>
Component:	mdadm	Assignee:	Jes Sorensen <Jes.Sorensen>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	agk, dledford, ed.ciechanowski, Jes.Sorensen, lukasz.dorau, maciej.patelczyk, pawel.baldysiak
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mdadm-3.2.6-19.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	956021	Environment:
Last Closed:	2013-07-05 02:08:15 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:	956021, 956031
Bug Blocks:

Description Jes Sorensen 2013-04-24 08:15:31 UTC

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

If rebuild of IMSM RAID5 volume is started in OROM, it does not proceed in OS.

Reproducible: Always

Steps to Reproduce:
1. Create IMSM RAID5 volume with 3 HDDs
2. Remove one hot swappable HDD from the array 
3. Replace failed HDD with a good HDD (do not add it to container)
4. Restart computer, enter RSTe RAID OROM interface
5. Choose newly added HDD and start Rebuild in OROM
5. Boot OS and check RAID status in OS

Actual Results:  
RAID5 volume is in Degraded state in OS. Rebuild has not been started.

Expected Results:  
RAID5 volume is being rebuilt in OS.

Comment 1 Fedora Update System 2013-04-24 14:05:10 UTC

mdadm-3.2.6-19.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/mdadm-3.2.6-19.fc17

Comment 2 Fedora Update System 2013-04-25 00:29:11 UTC

Package mdadm-3.2.6-19.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mdadm-3.2.6-19.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6527/mdadm-3.2.6-19.fc17
then log in and leave karma (feedback).

Comment 3 Fedora End Of Life 2013-07-04 07:43:38 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora Update System 2013-07-05 02:08:15 UTC

mdadm-3.2.6-19.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.