Bug 874722 - oo-admin-move fails
Summary: oo-admin-move fails
Keywords:
Status: CLOSED DUPLICATE of bug 847712
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 17:58 UTC by Kenny Woodson
Modified: 2015-05-15 02:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-08 20:10:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.