Description of problem: When deploying RHEL 7 to a bare metal machine using Opentack Kickstart Template, the OS install fails due to missing %end in 3 different locations and has a key --skip no longer appears to be valid. Version-Release number of selected component (if applicable): Used the following repo for testing: OpenStack/Foreman/2014-06-20.2/RHEL-6-Server-OS-Foreman How reproducible: Replicated on 2 different setups Steps to Reproduce: 1.Install Foreman and log into the UI 2.Create an OS for RHEL 7 and add the appropriate components 3. Use the OpenStack KickStart Template to deploy RHEL 7 to bare metal Actual results: OS install will stop with errors stating missing %end Expected results: RHEL 7 installed and operational Additional info:
A couple questions: * How did you install foreman? foreman-installer? staypuft-installer? foreman-server.sh? * which provisioning template did you use? The exact name, please. Can you attach the template? thanks
I used foreman_server.sh to install. In the OpenStack Provsioning UI, I select Hosts -> Provsioning templates and on Page 2, I am using OpenStack KickStart Template. I can attach the template if you tell me where they are stored.
Thanks, moving to that team.
Currently Foreman Provisioner kickstart for RHEL7 does not work. We need to fix it for release. Not sure if the same issue exists for Staypuft also.
This issue should not exist in staypuft. We have many people all deploying all against RHEL 7 with no kickstart issues. This is only an issue for the openstack-foreman-installer deployment method. Arkady, Is it acceptable in the short term to provide a working kickstart file? I can extract the staypuft kickstart or even point to an upstream kickstart file that will work. This should cover you until you make the switch to using staypuft.
Created attachment 931913 [details] Working RHEL7 Foreman ks template Attached is the working Openstack Kickstart Template we have been using to deploy RHEL 7 to provisioned nodes.
Mike, I have attached a working template to get RHEL7 provisioned to machines using the Foreman installer.
Mike, that will work. We will need 2 things to make it happen. 1. Steve R./John H. Pilot and PoC deployment guides should cover setting of Foreman to use it for provisioning. 2. Kickstart should be part of Foreman bits, not a separate file that Admin need to pull from somewhere. Thanks, Arkady
Steve, you're providing these kickstarts in a package, right? no code change needed in OFI?
Mike, John is developing new kickstarts for prong A , so nothing should be needed for prong A. spr
Verified fixed with final GA kickstart scripts.