Bug 1039278 (RHOS-Foreman-Deployability)

Summary: Tracker for all RHOS Foreman Deployability Issues
Product: Red Hat OpenStack Reporter: Perry Myers <pmyers>
Component: distributionAssignee: james labocki <jlabocki>
Status: CLOSED NOTABUG QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0CC: bholden, dcleal, markmc, srevivo
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-19 01:28:59 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: 1030077, 1030078, 1033140, 1033204, 1033208, 1033213, 1033217, 1033223, 1033225, 1033227, 1033242, 1033243, 1033245, 1033247, 1033249, 1033261, 1033264, 1039609, 1039611, 1045026    
Bug Blocks:    

Description Perry Myers 2013-12-07 13:43:25 UTC 
Description of problem:
jlabocki did some installation testing and uncovered some areas where we could improve deployability of RHOS via Foreman.  The issues he raised and filed bugs on are tracker via this bz.  Not all bugs will be resolved for RHOS 4 or 4.0.z.  So this Tracker can be used across RHOS releases.