Description of problem: After using a minimal fc23 image, vdsm installs ok but it fails no run getVDSCapabilities with 'No such file or directory', after some investigation, it turns out that it does not find numactl binary: vdsm vds ERROR unexpected error Traceback (most recent call last): File "/usr/share/vdsm/rpc/bindingxmlrpc.py", line 1232, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/rpc/bindingxmlrpc.py", line 513, in getCapabilities ret = api.getCapabilities() File "/usr/share/vdsm/API.py", line 1319, in getCapabilities c = caps.get() File "/usr/share/vdsm/caps.py", line 709, in get caps['numaNodeDistance'] = getNumaNodeDistance() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in __call__ value = self.func(*args) File "/usr/share/vdsm/caps.py", line 360, in getNumaNodeDistance retcode, out, err = utils.execCmd(['numactl', '--hardware']) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 648, in execCmd deathSignal=deathSignal, childUmask=childUmask) File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 63, in __init__ **kw) File "/usr/lib64/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 83, in _execute_child_v276 _to_close=to_close File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 118, in _execute_child_v275 restore_sigpipe OSError: [Errno 2] No such file or directory Version-Release number of selected component (if applicable): # rpm -qa vdsm vdsm-4.17.999-250.git0e1dd4f.fc23.noarch (vdsm custom build for master branch) How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: manually installing numactl works
Numa is SLA-related. Moving to SLA.
I see numactl on vdsm.spec but not on vdsm.spec.in $ grep numactl vdsm.spec | grep numactl Requires: numactl My spec.in resolved it and created it in vdsm.spec. Can you check yours?
I do not see it in 3.6 spec.in file. It was removed by https://gerrit.ovirt.org/40738 in favour of safelease package. And that package was broken on fc23. It was supposedly fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1287862 Can you please check whether it is still an issue?
Current vdsm master head does not add the Requires: numactl but still uses it in the code: dcaro@akhos$ grep numactl -n vdsm.spec 1208:%{_datadir}/%{vdsm_name}/tests/caps_numactl_4_nodes.out dcaro@akhos$ grep numactl -n vdsm/caps.py 271: retcode, out, err = commands.execCmd(['numactl', '--hardware']) 273: logging.error("Get error when execute numactl", exc_info=True)
VDSM does not depend on numactl directly. It depends on safelease and safelease depends on numactl. Please check the repo closure on F23.
let me retry again, but I tested the installation on a freshly install fedora23 cloud image, and it did not pull numactl in, I had to install it myself.
It seems that it's pulling it correctly, not sure why it did not before, might be a yum issue, looking, will reopen as yum issue if so