System has 1G disk where 100G is a swap file and the rest is root partition with some old limited 7.2 install (almost full). Selected "personal system" and asked anaconda to use the whole disk. It complained about not been able to. I guessed that there is not enough space. Problem 1. A better wording would be very helpful. Then I went to manual partitioning selected preserving existing root partition, went to package selection and trimmed down list of packages to around 700meg total. Started install but it says that over 500 meg is required on root partition. Well many files would have been owerwritten with the new versions but I understand that this part is exteremely hard to detect. So I switched to VT2, deleted almost all files, unmounted dev/pts and some other mounted from sysimage, then went to retry install and got traceback (attached).
Created attachment 68845 [details] anaconda dump file
Actually, the traceback is because you unmounted /dev/pts so when we went to unmount it with the rest of the filesystems, the unmounting failed
I'm not sure what the bug report is here - what is the issue you are reporting?
That is correct. I did unmount dev/pts, since I wanted to clean the disk up. I am reporting this because any kind of traceback is considered a bug. In this case, according to your information the umount error can be prevented if you check for the state of mount before calling unmount. In my scenario I was forced to start install over and repeat my package selection again.
So, is there going to be a check for presence of a mount point before issuing an unmount command?