Bug 2063923

Summary:	[PATCH] Confine numad to systems with actual numa nodes
Product:	Red Hat Enterprise Linux 9	Reporter:	Pat Riehecky <riehecky>
Component:	numad	Assignee:	Lukáš Nykrýn <lnykryn>
Status:	NEW ---	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, extras-qa, jwboyer
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:	2063922	Environment:
Last Closed:		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 Pat Riehecky 2022-03-14 16:15:22 UTC

+++ This bug was initially created as a clone of Bug #2063922 +++

Description of problem:

Currently it is trivial to start numad on systems that do not actually have numa awareness.  This includes a number of virtualization solutions.

Version-Release number of selected component (if applicable):numad-0.5-35.20150602git.fc35.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Fire up a VM without numa nodes
2. start numad
3. it runs but can't do anything causing wasted CPU/Memory

Actual results:

The numad.service starts on systems without numa nodes

Expected results:

The service is able to detect if numa is not present

Additional info:

This patch alters the requirements to ignore starting numad on systems where there are not nodes to migrate between.