Description of problem:

During install of RHEL5 x86_64 from disk, the ext2 filesystem where the isos 
are copied to is not unmounted before the %post section of ks.cfg is executed.

Version-Release number of selected component (if applicable):

Kernel 2.6.18-1.2739.el5

How reproducible:

Perform RHEL5 install from disk, where RHEL5 isos are copied to an ext2 
filesystem on a disk. In this case, the isos are copied to /dev/sda2.

Steps to Reproduce:
1. Start RHEL5 x86_64 install process, install from hard drive. In my case, 
the isos are on /dev/sda2.
2. Continue through install process and stop right before you start installing 
the rpms.
3. Change to one of the virtual consoles (Alt-F2) and on the command shell, 
type "df -k" to verify that /tmp/sda2 is mounted read-only.
4. Open the kickstart file (/tmp/ks.cfg) that is created and add code in the %
post section to pause the installation process. A nice infinite loop will do:

while [ -e /tmp/pause]; do
    sleep 10
done

5. Switch back to the main console and start the rpm installation process. Go 
back to the other virtual console and create /tmp/pause:

$ touch /mnt/sysimage/tmp/pause

6. Wait for the rpm install to finish and let it go into %post. Once there, 
type "df -k".
  
Actual results:

Filesystem on /tmp/sda2 is not unmounted before %post section of ks.cfg 
executes.

Expected results:

Filesystem on /tmp/sda2 should not be mounted when %post section of ks.cfg 
executes.

Additional info:

The anaconda process that performs the install is:

/usr/bin/python /usr/bin/anaconda -m hd://sda2.ext2// --graphical --selinux --
kickstart /tmp/ks.cfg --lang en_US --keymap us

I did not test x86, but I'm assuming the problem is there too.

The reason why this is a problem for us is because we reclaim the partition 
where the isos are located. In order to do that, the partition must not be 
mounted. We can work around this issue by adding some umount commands to our 
kickstart file, but in RHEL4 we do not run into this problem.