This bug was initially created as a copy of Bug #2149292

I am copying this bug because: 
The problem can be reproduced also on RHEL-8.8.0-20221128.0 with mdadm-4.2-6.el8.



Description of problem:
Installation fails with a traceback when reinstalling a system with a RAID device from a previous installation:

...
INFO:program:Running [53] mdadm --zero-superblock /dev/vda3 ...
INFO:program:stdout[53]: 
INFO:program:stderr[53]: mdadm: Couldn't open /dev/vda3 for write - not zeroing

INFO:program:...done [53] (exit code: 2)
INFO:anaconda.threading:Thread Failed: AnaTaskThread-CreateStorageLayoutTask-1 (140220576028224)
ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-CreateStorageLayoutTask-1 has failed: Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/gi/overrides/BlockDev.py", line 1093, in wrapped
    ret = orig_obj(*args, **kwargs)
gi.repository.GLib.GError: g-bd-utils-exec-error-quark: Process reported exit code 2: mdadm: Couldn't open /dev/vda3 for write - not zeroing
 (0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/pyanaconda/threading.py", line 275, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.9/threading.py", line 917, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/task.py", line 96, in _thread_run_callback
    self._task_run_callback()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/task.py", line 109, in _task_run_callback
    self._set_result(self.run())
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/installation.py", line 86, in run
    self._turn_on_filesystems(
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/installation.py", line 166, in _turn_on_filesystems
    storage.do_it(callbacks)
  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/blivet.py", line 115, in do_it
    self.devicetree.actions.process(callbacks=callbacks, devices=self.devices)
  File "/usr/lib/python3.9/site-packages/blivet/actionlist.py", line 47, in wrapped_func
    return func(obj, *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/actionlist.py", line 284, in process
    action.execute(callbacks)
  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/deviceaction.py", line 760, in execute
    self.format.destroy()
  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/formats/__init__.py", line 553, in destroy
    self._destroy(**kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/blivet/formats/mdraid.py", line 92, in _destroy
    blockdev.md.destroy(self.device)
  File "/usr/lib64/python3.9/site-packages/gi/overrides/BlockDev.py", line 1115, in wrapped
    raise transform[1](msg)
gi.overrides.BlockDev.MDRaidError: Process reported exit code 2: mdadm: Couldn't open /dev/vda3 for write - not zeroing


Version-Release number of selected component (if applicable):
RHEL-9.2.0-20221128.3
python-blivet-3.6.0-3.el9

How reproducible:
Always

Steps to Reproduce:
1. Have a system with rootfs on RAID1, an example kickstart partitioning:

clearpart --all --initlabel
part /boot --asprimary --size=500 --label=boot
part swap --fstype=swap --recommended --label=swap
part raid.01 --size=8000
part raid.02 --size=8000
raid / --device=0 --level=RAID1 raid.01 raid.02

2. Try to re-install the system using autopart:

clearpart --all --initlabel
autopart


Actual results:
Anaconda traceback

Expected results:
RAID removed and new partitioning successfully created.