Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1113766

Summary: Foreman Openstack Kickstart Template deploying RHEL 7 has issues
Product: Red Hat OpenStack Reporter: Kurt Hey <kurt_hey>
Component: openstack-foreman-installerAssignee: joherr
Status: CLOSED CURRENTRELEASE QA Contact: Ami Jeain <ajeain>
Severity: high Docs Contact:
Priority: high    
Version: Foreman (RHEL 6)CC: aberezin, arkady_kanevsky, cdevine, jdonohue, joherr, kschinck, kurt_hey, mburns, morazi, randy_perryman, rhos-maint, sreichar, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard: pre-MVP
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-14 14:37:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1093544, 1122184, 1128481    
Attachments:
Description Flags
Working RHEL7 Foreman ks template none

Description Kurt Hey 2014-06-26 20:57:14 UTC 
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:
Comment 2 Mike Burns 2014-06-27 01:21:08 UTC 
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
Comment 3 Kurt Hey 2014-06-27 11:38:08 UTC 
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.
Comment 4 Mike Burns 2014-06-27 11:53:41 UTC 
Thanks, moving to that team.
Comment 6 arkady kanevsky 2014-08-27 19:11:16 UTC 
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.
Comment 7 Mike Burns 2014-08-27 22:42:19 UTC 
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.
Comment 8 Kurt Hey 2014-08-28 12:08:43 UTC 
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.
Comment 9 Kurt Hey 2014-08-28 12:09:46 UTC 
Mike, I have attached a working template to get RHEL7 provisioned to machines using the Foreman installer.
Comment 10 arkady kanevsky 2014-08-28 13:37:41 UTC 
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
Comment 12 Mike Burns 2014-09-12 19:01:55 UTC 
Steve,  you're providing these kickstarts in a package, right?  no code change needed in OFI?
Comment 13 Steve Reichard 2014-09-18 13:58:50 UTC 
Mike,

John is developing new kickstarts for prong A , so nothing should be needed for prong A.

spr
Comment 14 Kurt Hey 2014-11-14 14:37:12 UTC 
Verified fixed with final GA kickstart scripts.