Bug 874722

Summary:	oo-admin-move fails
Product:	OKD	Reporter:	Kenny Woodson <kwoodson>
Component:	Pod	Assignee:	Dan McPherson <dmcphers>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	mwoodson, twiest
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-08 20:10:09 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 Kenny Woodson 2012-11-08 17:58:02 UTC

Description of problem:
When attempting to do some district compaction I was investigating a few failed moves in the logs.  

I was seeing this message in the mcollective.log on the destination node of the move:

oo_app_destroy' Unable to setup pam/fs/nproc limits for <gear uuid>

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

How reproducible:
I'm seeing this every time.

Steps to Reproduce:
1. Run this command:
(/bin/date ; /usr/sbin/oo-admin-move --gear_uuid <uuid>) 2>&1 | /usr/bin/tee -a oo-admin-move-log--<uuid>

2. Look in the mcollective.log on the destination host.
3. 
  
Actual results:
Moves are failing.  

Expected results:
Move succeeds.  

Additional info:

I'm not 100% sure if this is related as moves fail and then upon retry they succeed.

Comment 1 Dan McPherson 2012-11-08 20:10:09 UTC


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