Description of problem:
After going through the full rhel-osp-installer install that is started on LiveCD bootup I click "Install to Hard Drive" and nothing happens.
Version-Release number of selected component (if applicable):
Run installer, without without networking (ie manual networking as well).
Steps to Reproduce:
1. Boot LiveCD
2. Run through installer in terminal window.
3. Complete installer.
4. Double click "Install to Hard Drive"
Configured image is written to disk and livecd install reboots. I expect to see a working foreman install with all the settings i just entered.
I tried running liveinst from the console (as root) and it didn't work. I did an xhost+ and that allowed anaconda to start. Running anaconda the following happened:
The installer starts up. I hit the first "next" and instantly get the error dialog:
"An error occurred when attempting to load an installer interface component.
className = Keyboard Window"
I can choose "exit" or "retry." Retry brings the dialog back. Exit brings me to a "The system will now reboot" dialog with a big "Reboot" button. Clicking it does nothing but exit the installer.
Some additional notes, seems as if liveinst require NetworkManager to be running. For anything to work i need to run xhost+ and /etc/init.d/NetworkManager start first.
Could this be something about my test environment? (Fusion Pro). Is this a graphics issue maybe?
We really shouldn't put the install to disk option on the desktop. It will (if working correctly) install the base image to disk, but not the just deployed foreman instance.
A longer term goal would be to make it write the current state to disk.
*** Bug 1125770 has been marked as a duplicate of this bug. ***
*** Bug 1127012 has been marked as a duplicate of this bug. ***
I've committed a fix to remove the icon to the desktop to the rhelosp-installer-live distgit repo.
Based on comment #4 and comment #8 - I understand that the "Install to Hard Drive" button shouldn't exist on the desktop and it doesn't.
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.