Description of problem: I discovered a pxe-less host (with and w/o dhcp). Host was discovered successfully. However when I click on provision to provision the host with rhel67 os, I didn't see the kexec on the installer. On host console, discovery status was appearing and after a few minutes host rebooted and a login screen appears. On login, I can all anaconda-cfg.ks file and install.log file. So missing thing is user won't be able to see installer progress from console. User would get Discovery status screen to login prompt. However if I provision the discovered host with rhel7 then I can see anaconda installer and install progress on console like package installation and post install steps. Version-Release number of selected component (if applicable): Sat 6.1.5 compose3(Satellite-6.1.0-RHEL-7-20151204.0) rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch rubygem-smart_proxy_discovery-1.0.3-2.el6.noarch ruby193-rubygem-foreman_discovery-2.0.0.22-1.el6_6sat.noarch foreman-discovery-image-3.0.5-3.el7sat.noarch How reproducible: always Steps to Reproduce: 1. discovered a pxe-less host 2. provision it with rhel67 3. Actual results: User won't be able to see installer progress like package install or post-install on console. Directly login screen appears after Discovery Status screen. It creates a weird situation, like If I see at console whether provisioning started, I won't get any clue because I see the status screen. However If I wait for some-time, direct login screen appears. It means provisioning works but without showing anaconda installer progress. Expected results: Installer progress should be visible on host console while provisioning a pxe-less discovered host with rhel67 Additional info:
Ack, not a blocker.
Created redmine issue http://projects.theforeman.org/issues/12733 from this bug
Note: this is the issue only with provisioning of pxe-less hosts. I can see installer progress while provisioning of pxe-based discovered hosts.
Moving 6.2 bugs out to sat-backlog.
Isn't this the same as https://bugzilla.redhat.com/show_bug.cgi?id=1508455 ?
Yes it is, feel free to verify or close as dupe.
A duplicate for this one got resolved and verified. https://bugzilla.redhat.com/show_bug.cgi?id=1508455
*** This bug has been marked as a duplicate of bug 1508455 ***