Activity log for bug #1860753

Date Who What changed Old value New value Message
2020-01-24 06:46:20 serenico bug added bug
2020-01-24 06:47:14 serenico description When enabling 'memory_tracker' service and using Python3, memory_tracker.sh failts to run because tools/mlock_report.py is unable to import psutil module: 2020-01-23 19:16:50.727 | + functions-common:service_check:1622 : sudo systemctl is-enabled devstack@memory_tracker.service 2020-01-23 19:16:50.777 | enabled 2020-01-23 19:16:50.789 | + functions-common:service_check:1626 : sudo systemctl status devstack@memory_tracker.service --no-pager 2020-01-23 19:16:50.838 | ● devstack@memory_tracker.service - Devstack devstack@memory_tracker.service 2020-01-23 19:16:50.839 | Loaded: loaded (/etc/systemd/system/devstack@memory_tracker.service; enabled; vendor preset: disabled) 2020-01-23 19:16:50.839 | Active: failed (Result: exit-code) since Thu 2020-01-23 19:15:20 UTC; 1min 30s ago 2020-01-23 19:16:50.839 | Main PID: 28314 (code=exited, status=1/FAILURE) 2020-01-23 19:16:50.839 | 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: [[[ 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: Thu Jan 23 19:15:20 UTC 2020 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: --- 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: Traceback (most recent call last): 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: File "/opt/stack/devstack/tools/mlock_report.py", line 7, in <module> 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: import psutil 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: ImportError: No module named psutil 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: devstack@memory_tracker.service: main process exited, code=exited, status=1/FAILURE 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: Unit devstack@memory_tracker.service entered failed state. 2020-01-23 19:16:50.840 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: devstack@memory_tracker.service failed. My best guess is that the python script is using python command, while devstack made available psutil package to python3 command. I think DevStack should now use 'python3' command by default and use 'python' command only as failback interpreter. When enabling 'memory_tracker' service and using Python3, memory_tracker.sh fails to run because tools/mlock_report.py is unable to import psutil module: 2020-01-23 19:16:50.727 | + functions-common:service_check:1622 : sudo systemctl is-enabled devstack@memory_tracker.service 2020-01-23 19:16:50.777 | enabled 2020-01-23 19:16:50.789 | + functions-common:service_check:1626 : sudo systemctl status devstack@memory_tracker.service --no-pager 2020-01-23 19:16:50.838 | ● devstack@memory_tracker.service - DevStack devstack@memory_tracker.service 2020-01-23 19:16:50.839 | Loaded: loaded (/etc/systemd/system/devstack@memory_tracker.service; enabled; vendor preset: disabled) 2020-01-23 19:16:50.839 | Active: failed (Result: exit-code) since Thu 2020-01-23 19:15:20 UTC; 1min 30s ago 2020-01-23 19:16:50.839 | Main PID: 28314 (code=exited, status=1/FAILURE) 2020-01-23 19:16:50.839 | 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: [[[ 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: Thu Jan 23 19:15:20 UTC 2020 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: --- 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: Traceback (most recent call last): 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: File "/opt/stack/devstack/tools/mlock_report.py", line 7, in <module> 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: import psutil 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 memory_tracker.sh[28314]: ImportError: No module named psutil 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: devstack@memory_tracker.service: main process exited, code=exited, status=1/FAILURE 2020-01-23 19:16:50.839 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: Unit devstack@memory_tracker.service entered failed state. 2020-01-23 19:16:50.840 | Jan 23 19:15:20 centos-7-fortnebula-regionone-0014112762 systemd[1]: devstack@memory_tracker.service failed. My best guess is that the python script is using python command, while DevStack made available psutil package to python3 command. I think DevStack should now use 'python3' command by default and use 'python' command only as fallback interpreter.
2020-01-24 08:30:23 OpenStack Infra devstack: status New In Progress
2020-01-24 08:30:23 OpenStack Infra devstack: assignee Radosław Piliszek (yoctozepto)
2020-01-24 08:49:51 OpenStack Infra devstack: assignee Radosław Piliszek (yoctozepto) Federico Ressi (fressi-redhat)
2020-01-28 19:03:06 OpenStack Infra devstack: assignee Federico Ressi (fressi-redhat) Ian Wienand (iwienand)
2020-01-30 12:35:46 OpenStack Infra devstack: assignee Ian Wienand (iwienand) Federico Ressi (fressi-redhat)
2020-01-31 05:57:27 OpenStack Infra devstack: status In Progress Fix Released