Red Hat Bugzilla – Bug 1299815
'Kickstart insufficient' on Installation Destination when installing from iso
Last modified: 2016-09-13 12:24:21 EDT
Description of problem:
After I start installing from ISO, an Installation Summary screen shows, and there is an error under the Installation Destination:
and an orange triangle is displayed.
The disk, according to the installer, has 465.76 GiB. There was previous installation of OSP node present on the disk, but I was able to delete it within the installer.
After I tried to run the installer with manual partitioning done by me, a few seconds later there is an error:
"IOException: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernal og the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes."
Version-Release number of selected component (if applicable):
Hit this on both install isos
Steps to Reproduce:
1. Use the machines as a OSP nodes in an RHELOSP deployment
2. Connect the ISO to the machine, restart
3. Boot from the installation ISO and start the installation
Kickstart insufficient and then IOException when storage configured manually
No error; partitions created by kickstart; install continues and finishes successfully
Workaround is to create the partitioning manually, start the installation, hit the error, restart the machine and run the ISO again. It then works as it should.
When I just restarted the machine and ran the ISO again, the same problem appeared.
The installer does a clearpart; not sure why it's not wiping the disk as I regularly reuse my system without issue. Can you try to reproduce this and provide the anaconda logs?
I just started the installation on a host that was previously an OSP node, it's currently installing RHCI.
Will investigate further during GA.
Unable to reproduce the issue. Marking as verified.
Tested on QCIOOO-8.0-RHEL-7-20160823.t.0 + QCI-1.0-RHEL-7-20160825.t.0.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.