Bug 765728

Summary:	Need to export all virt-who env variables in virt-who-initscript
Product:	Red Hat Enterprise Linux 5	Reporter:	Keqin Hong <khong>
Component:	virt-who	Assignee:	Radek Novacek <rnovacek>
Status:	CLOSED ERRATA	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.8	CC:	cshao, gouyang, huiwang, leiwang, moli, ovasik, ycui
Target Milestone:	rc	Keywords:	TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virt-who-0.5-1.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-21 06:07:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	715031, 754330, 759462, 769266

Description Keqin Hong 2011-12-09 09:06:52 UTC

Description of problem:
Current virt-who-initscript (install virt-who-initscript $(DESTDIR)/etc/rc.d/init.d/virt-who
)  exported only two env vars: 
"
export VIRTWHO_BACKGROUND
export VIRTWHO_DEBUG
"

As a result, virt-who on rhev-h is not to able to work properly since VIRTWHO_VDSM env var is not exported.

Version-Release number of selected component (if applicable):
virt-who-0.4

How reproducible:
100%

Steps to Reproduce:
1. # grep export virt-who-initscript 
export VIRTWHO_BACKGROUND
export VIRTWHO_DEBUG

2.
3.
  
Actual results:
exported only two env vars: VIRTWHO_BACKGROUND and VIRTWHO_DEBUG

Expected results:
export all env of /etc/sysconfig/virt-who

Remove hardcoded exports. program to export all items in /etc/sysconfig/virt-who

Additional info:

Comment 2 Radek Novacek 2011-12-13 14:34:26 UTC

This bug should be fixed in virt-who-0.5-1.el5

https://brewweb.devel.redhat.com/taskinfo?taskID=3889752

Comment 5 errata-xmlrpc 2012-02-21 06:07:06 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/RHEA-2012-0225.html