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

Bug 1478014

Summary:	Swift containers are stuck restarting
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED DUPLICATE	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	12.0 (Pike)	CC:	cschwede, dbecker, derekh, mburns, morazi, pgrist, rhel-osp-director-maint, srevivo, thiago, zaitcev
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	scale_lab
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 01:39:49 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 Sai Sindhur Malleni 2017-08-03 13:04:18 UTC

Description of problem: Some swift containers on controller-0 are stuck restarting as follows 
https://gist.github.com/smalleni/47bea700ad4b6fe5c1d438e93926a9a5

Using docker log to probe  the logs I see messages such as 
https://gist.github.com/smalleni/87291895763f8033cfb7ee811e860d60
https://gist.github.com/smalleni/a1bb00762c29e1125378ce183464d405
on the containers stuck restarting

Version-Release number of selected component (if applicable):
OSP 12 Build 2017-07-27.1

How reproducible:


Steps to Reproduce:
1. Deploy OSP 12 with containers
2.
3.

Actual results:
Some swift containers are stuck restarting

Expected results:
Containers should run normally

Additional info:

Comment 1 Pete Zaitcev 2017-08-03 18:45:58 UTC

Logs captured by the reporter point at rings absent. It's hardly anything
Swift can do anything about. I'm switching the component to Director, so
relevant developers are aware of the problem.

Comment 4 Thiago da Silva 2017-08-10 01:39:49 UTC


*** This bug has been marked as a duplicate of bug 1474866 ***