Bug 1315184

Summary: After poweroff and poweron vm with numactl package numactl -H not show me any information
Product: Red Hat Enterprise Linux 7 Reporter: Artyom <alukiano>
Component: numactlAssignee: Pingfan Liu <piliu>
Status: CLOSED ERRATA QA Contact: Leos Pol <lpol>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.2CC: ovasik, piliu, ruyang, skozina
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: numactl-2.0.12-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:59:58 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: 1394638, 1400961, 1404314, 1442974, 1472889, 1647768    
Attachments:
Description Flags
sosreport none

Description Artyom 2016-03-07 07:42:27 UTC 
Description of problem:
I have vm with numactl package and after poweroff and poweron vm numactl -H does not show me any information about numa node. If I reinstall numactl package(yum erase numactl && yum install numactl), it show me normal information(that my vm has one numa node and information about node memory and cpu).

Version-Release number of selected component (if applicable):
3.10.0-327.13.1.el7.ppc64le
numactl-2.0.9-6.el7_2.ppc64le
numactl-libs-2.0.9-6.el7_2.ppc64le

How reproducible:
always

Steps to Reproduce:
1. Install on vm numactl package
2. Poweroff and poweron vm
3. run numactl -H

Actual results:
nohing

Expected results:
available: 1 nodes (0)
node 0 cpus: 0
node 0 size: 1024 MB
node 0 free: 368 MB
node distances:
node   0 
  0:  10

Additional info:

Before package reinstall:
[root@dhcp167-130 ~]# numactl -H
nothing

After package reinstall:
[root@dhcp167-130 ~]# yum erase numactl -y && yum install numactl -y
[root@dhcp167-130 ~]# numactl -H
available: 1 nodes (0)
node 0 cpus: 0
node 0 size: 1024 MB
node 0 free: 368 MB
node distances:
node   0 
  0:  10
Comment 1 Artyom 2016-03-07 07:45:07 UTC 
Created attachment 1133662 [details]
sosreport

I do not sure what logs you need, so I just attach sosreport.
If you need any other information I will glad to help you.
Comment 3 Petr Holasek 2016-03-07 11:02:10 UTC 
Hi Artyom,

in which point you made the sosreport? When numactl -H output was empty or after restart?
Comment 4 Artyom 2016-03-07 13:20:07 UTC 
1) Installed package and checked numactl -H - output exists
2) Poweroff, poweron VM and checked numactl -H - output does not exist
3) Reinstall package and checked numactl -H - output exists
4) ran sosreport command
If you need it on some other point of time give me know.
Comment 11 Pingfan Liu 2019-02-26 06:24:11 UTC 
*** Bug 1678561 has been marked as a duplicate of this bug. ***
Comment 13 Pingfan Liu 2019-06-03 06:18:00 UTC 
Hi Leos,

I remember to reproduce this bug on a LPAR machine. And after rebasing, it is fixed. I will try to fetch one LPAR to reproduce it.
Also set need info from reporter.
Comment 16 errata-xmlrpc 2019-08-06 12:59:58 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/RHBA-2019:2156
Comment 17 Artyom 2019-10-23 09:00:11 UTC 
Maybe it was connected to the fact that I poweroff it via oVirt, so it just destroyed the VM instance.