Bug 1238423

Summary: migration error "Process ID out of range error" after evmserverd start
Product: Red Hat CloudForms Management Engine Reporter: Josh Carter <jocarter>
Component: ApplianceAssignee: Nick Carboni <ncarboni>
Status: CLOSED ERRATA QA Contact: Jan Krocil <jkrocil>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4.0CC: abellott, jhardy, mfeifer, obarenbo, snansi
Target Milestone: GA   
Target Release: 5.5.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.5.0.1 Doc Type: Bug Fix
Doc Text:
While migrating from the previous version of CloudForms Management Engine, a process id out of range error would be displayed after the evmserverd service was started. This error was a result of invalid text being written to the evm pid file by the upgrade process. This error was fixed by verifying the content of the pid file before passing it to ps. The process id out of range error is no longer seen in the new version of CloudForms Management Engine.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 13:21:07 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 Josh Carter 2015-07-01 20:14:49 UTC 
Description of problem:
Migrate from 5.3.4 to 5.4.0.5 using https://access.redhat.com/articles/1435433

Section "Upgrade and Migration Procedure from 5.3.1 and above"
The start of the evmserverd service will generate the following error. 

"Process ID out of range error"

A #service evmserverd status shows all workers started without error. 

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


How reproducible:
very

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Nick Carboni 2015-07-10 20:29:53 UTC 
Was not able to reproduce by following the directions in the KB article exactly.

For this to happen, you would need to run yum update from the command line without stopping the server first then continue with the commands listed in step 5 of "Upgrade and Migration Procedure from 5.3.1 and above."

https://github.com/ManageIQ/manageiq/pull/3417
Comment 7 CFME Bot 2015-07-13 13:12:24 UTC 
New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/653fd8523288b8dda8c702f6204871fa3ea6fdab

commit 653fd8523288b8dda8c702f6204871fa3ea6fdab
Author:     Nick Carboni <ncarboni>
AuthorDate: Fri Jul 10 16:16:45 2015 -0400
Commit:     Nick Carboni <ncarboni>
CommitDate: Fri Jul 10 16:16:45 2015 -0400

    Make PidFile#pid return nil for non-numeric pid file contents
    
    If we return a non-numeric pid from PidFile#pid MiqProcess.command_line will cause ps(1)
    to output a usage message.
    This usage message was seen during the upgrade process if the server was started
    through the command line.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1238423

 lib/pid_file.rb           | 2 +-
 spec/lib/pid_file_spec.rb | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)
Comment 10 errata-xmlrpc 2015-12-08 13:21:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:2551