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

RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1051113

Summary:	missing catch_errors middleware from the default config file
Product:	[Community] RDO	Reporter:	Attila Fazekas <afazekas>
Component:	openstack-swift	Assignee:	Pete Zaitcev <zaitcev>
Status:	CLOSED RAWHIDE	QA Contact:	Dafna Ron <dron>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	derekh, pasik, yeylon, zaitcev
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-02 21:18:39 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:

Description Attila Fazekas 2014-01-09 17:36:04 UTC

Description of problem:

catch_errors is responsibly for setting up the x-trans-id if it is otherwise missing from the response, it is very helpful in trouble shooting.
Also this middleware responsible for the correct final error handling. 

Version-Release number of selected component (if applicable):

openstack-swift-proxy-1.11.0-1.fc21.noarch (probably several older version is affected)

How reproducible:
always

Steps to Reproduce:
1. yum install openstack-swift-proxy
2. grep pipeline.*catch_errors /etc/swift/proxy-server.conf || echo missing

Actual results:
/etc/swift/proxy-server.conf very different from the upstream sample config,
also the comments are missing.

Expected results:
The default config is closer to the upstream default and it contains the 

Additional info:
packstack also does not adds the catch_errors to the beginning of the swift-proxy.conf [pipeline:main]  pipeline.

Comment 1 Pete Zaitcev 2014-06-23 23:24:33 UTC

Since this bug was entered, upstream started forcing catch_errors
into the pipeline. So the functional problem is solved in 1.13.

However, I'm going to update the proxy-server.conf anyway, so that
the warning message is not printed.

Note that Puppet modules override our proxy-server.conf. If a fix in
Packstack or Foreman installation is desired, the bug needs cloning
against appropriate products and components.

Comment 3 Pete Zaitcev 2015-02-02 21:18:39 UTC

Modified in openstack-swift-2.2.0-4.fc22. Also, closing.