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

Bug 1208579

Summary:	Forman installer for OpenStack installs Swift Proxy but no Swift Service
Product:	Red Hat OpenStack	Reporter:	Greg Blomquist <gblomqui>
Component:	openstack-foreman-installer	Assignee:	Jason Guiditta <jguiditt>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0 (Juno)	CC:	gblomqui, mburns, morazi, rhos-maint, srevivo, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-08 13:55:51 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:	1208373

Description Greg Blomquist 2015-04-02 15:00:11 UTC

According to bug #1208373, the Foreman Installer for OpenStack sets up a Swift proxy, but does not setup the actual Swift service.

The end result is that Keystone believes that Swift is running and tells external clients that Swift is running, but when clients attempt to connect to the Swift service, clients get a 503 error.

Additionally, according to the reporter for bug #1208373 the Foreman Installer for OpenStack does not allow users to configure Swift.

Expected Results:

Either the Foreman Installer for OpenStack should fully configure the Swift service, or the installer should not configure Swift at all.  It shouldn't configure a proxy for Swift without setting up the Swift service.

Comment 6 Jason Guiditta 2015-09-15 16:36:38 UTC

Based on the referenced bug, I am not sure there is any actual bug here, aside from perhaps an RFE to not create the service endpoint if the service is not configured (which, at this point in the lifecycle of this product, I am pretty sure we would not implement).  The Staypuft release of ofi does not even offer the option to enable swift, that only happens in pure ofi-based installs, which I believe have a very limited support scope.  Even those typically would expect the user to hook up the proxy to some swift storage, though we do not configure a swift storage server.  I would propose we closed this bug if you are not opposed.