Bug 1047652

Summary:	openstack-foreman: foreman doesn't start tgt daemon automatically
Product:	Red Hat OpenStack	Reporter:	Yogev Rabl <yrabl>
Component:	openstack-foreman-installer	Assignee:	Jason Guiditta <jguiditt>
Status:	CLOSED WORKSFORME	QA Contact:	Ami Jeain <ajeain>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.0	CC:	augol, morazi, nlevinki, ohochman, rhos-maint, yeylon, yrabl
Target Milestone:	---
Target Release:	5.0 (RHEL 7)
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-22 19:36:44 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:	1064889

Description Yogev Rabl 2014-01-01 15:33:17 UTC

Description of problem:
The TGT daemon is essential for Cinder in order to work with the instances. The TGT must be up and running and configured in the chkconfig. 

The Foreman version: 
foreman-proxy-1.3.0-3.el6sat.noarch

Comment 2 Jason Guiditta 2014-02-04 20:59:31 UTC

Are you still encountering this problem?  Someone else hit this, and I believe it was the result of some bad configuration of cinder (I don't recall if it was a foreman configuration of cinder bug, or just different params needed).  After fixing config, the tgt service started as expected.

Comment 3 Mike Orazi 2014-05-22 19:36:44 UTC

Given that this wasn't responded to we believe this is no longer an issue.  Please re-open if this comes back.

Comment 4 Amit Ugol 2018-05-02 10:52:17 UTC

closed, no need for needinfo.