Bug 847547

The missing partition is a red herring; it's only not there because the action-sorting step put its creation after the luksFormat step.

I'm now trying to figure out how to create an update.img with a crypto.py that implements dolog...

Okay, got it.  (Sort of.)

I now see that a relevant point is that I've been working on creating some automatic kickstart files, the testing of which involves re-installing over and over with substantially similar configurations.  In particular, the partitioning is identical from one instance to the next.

So when the new partitions are created, they pick up exactly what was there before, so the raid-1 image then also has exactly what it had before, which was a LUKS image.  The cryptsetup code, down below _crypt_format_luks1() somewhere, sees the existing LUKS image and returns an EINVAL.

The answer is to wipe the LUKS image first.  I ended up creating this script:

#!/bin/sh
echo "scanning md devices..."
for d in /dev/md*; do
  [[ -b ${d} ]] || continue
  h=$(dd if=${d} of=/dev/stdout bs=4 count=1 2>/dev/null)
  if [[ "${h}" == "LUKS" ]]; then
    echo "Device ${d} looks suspicious"
    dd if=/dev/zero of=${d} bs=1024 count=1 2>/dev/null
  fi
done
echo "... scan done"

and calling it from a %pre section.  This is a crude hammer -- it'll wipe whatever LUKS systems it finds -- but it works for my autoinstalls.


What I don't get is why this doesn't come up in other cases, like a non-raided simple partition.  But I have another challenge to go on to...


I'm leaving this 'NEW' because the work-around is just that.  A better solution might be to add another storage 'action' between 'Create Device mdarray md<N>' and 'Create Format luks on mdarray md<N>' which just zeroes a page as above.

We actually do this exact thing for new partitions, but not for other new devices. We should be doing it regardless of device type.

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.

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.