Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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.
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.
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.
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