Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1272699

Summary:	virtualization-poller use heavy-weight check for libvirtd
Product:	[Community] Spacewalk	Reporter:	Tomasz Torcz <tomek>
Component:	Clients	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.4
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-29 17:03:12 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:
Bug Depends On:
Bug Blocks:	1484117

Description Tomasz Torcz 2015-10-17 19:06:52 UTC

Description of problem:
poller.py checks for running libvirtd with following command:

 if (subprocess.call(['/sbin/service','libvirtd','status'],

on contemporary Linux systems, this has a side effect of pulling logs to display for administration.  This is completely unnecessary in script usage.
Above check should be replaced by running:

 systemctl is-active libvirtd

Or even using D-Bus interface of systemd directly, without forking external program.

Version-Release number of selected component (if applicable):
rhn-virtualization-host-5.4.55-1.fc22.noarch

Comment 1 Tomasz Torcz 2016-04-29 17:03:12 UTC

I'm no longer interested in Spacewalk.

Comment 2 Eric Herget 2017-09-28 18:07:49 UTC

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.