Bug 952089 - [vdsm] vdsm pid should be printed to vdsm log when service starts
Summary: [vdsm] vdsm pid should be printed to vdsm log when service starts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Assaf Muller
QA Contact: Elad
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-15 07:34 UTC by Elad
Modified: 2016-02-10 19:16 UTC (History)
11 users (show)

Fixed In Version: vdsm-4.10.3-0.416.git5358ed2.el6.x86_64
Doc Type: Bug Fix
Doc Text:
When the vdsm process came up, the VDSM log did not contain the new PID of vdsmd. Now when VDSM starts it now outputs to the VDSM log: "MainThread::INFO::2013-05-05 11:57:38,609::vdsm::89::vds::(run) (PID: 14576) I am the actual vdsm...".
Clone Of:
Environment:
Last Closed: 2014-01-21 16:06:39 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:
amuller: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0040 0 normal SHIPPED_LIVE vdsm bug fix and enhancement update 2014-01-21 20:26:21 UTC
oVirt gerrit 14430 0 None None None 2020-09-10 12:53:23 UTC

Description Elad 2013-04-15 07:34:39 UTC 
Description of problem:

When vdsm process comes up, vdsm log should contain the new PID of vdsmd:

  
Actual results:

MainThread::INFO::2013-04-15 08:02:09,266::vdsm::89::vds::(run) I am the actual vdsm 4.10-1.6 tigris01.scl.lab.tlv.redhat.com (2.6.32-358.2.1.el6.x86_64)



Expected results:
My suggestion: 

MainThread::INFO::2013-04-15 08:02:09,266::vdsm::89::vds::(run) (PID:_) I am the actual vdsm 4.10-1.6 tigris01.scl.lab.tlv.redhat.com (2.6.32-358.2.1.el6.x86_64)
Comment 1 Elad 2013-06-24 06:22:41 UTC 
MainThread::INFO::2013-06-16 16:49:22,718::vdsm::92::vds::(run) (PID: 15051) I am the actual vdsm 4.11.0-34.gita6ea2d4.el6 nott-vds2.qa.lab.tlv.redhat.com (2.6.32-358.el6.x86_64)


verified on vdsm-4.11.0-46.gitd08ef2d3.el6.x86_64
Comment 2 Charlie 2013-11-28 00:31:52 UTC 
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 3 errata-xmlrpc 2014-01-21 16:06:39 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.

http://rhn.redhat.com/errata/RHBA-2014-0040.html
Note You need to log in before you can comment on or make changes to this bug.