Segmentation fault for client library "python-keystoneclient" on Linux Alpine (docker and vagrant image)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hello everyone,
I am currently experiencing a repeated bug with the python-
In order to reproduce the bug, follow the steps:
1- Get an alpine linux either on Docker or Vagrant. Please find the detailed steps here: https:/
2- On your python shell, after installing the needed dependencies, do something as simple as: "from keystoneclient import client", "from keystoneclient.v2_0 import client", or "from keystoneclient.v3 import client". All three of these tests should result in a segmentation fault.
3- You can get some limited additional info from gdb.
Thanks to anyone who would help.
- Update: Confirmed and reproducible, here is a complete description and first memory core dump https:/
#0 0x00006453b6c2d7b9 in __vdsosym (vername=
name=
#1 0x00006453b6c64e5e in __clock_gettime (clk=1, ts=0x6453b79c1be0)
at src/time/
#2 0x00006453b6edf37e in ffi_call_unix64 () from /usr/lib/
#3 0x00006453b6edef48 in ffi_call () from /usr/lib/
#4 0x00006453b70f0e67 in _ctypes_callproc ()
from /env/lib/
#5 0x00006453b70ebce4 in ?? () from /env/lib/
#6 0x00006453bb4e8654 in PyObject_Call () from /usr/lib/
#7 0x00006453bb560257 in PyEval_EvalFrameEx ()
from /usr/lib/
#8 0x00006453bb55edbd in PyEval_EvalFrameEx ()
from /usr/lib/
#9 0x00006453bb560aae in PyEval_EvalCodeEx ()
from /usr/lib/
#10 0x00006453bb560b15 in PyEval_EvalCode () from /usr/lib/
#11 0x00006453bb56d6d0 in PyImport_
from /usr/lib/
#12 0x00006453bb56dade in ?? () from /usr/lib/
#13 0x00006453bb56e2f9 in ?? () from /usr/lib/
#14 0x00006453bb56e513 in ?? () from /usr/lib/
#15 0x00006453bb56ef93 in PyImport_
from /usr/lib/
#16 0x00006453bb557530 in ?? () from /usr/lib/
#17 0x00006453bb4e8654 in PyObject_Call () from /usr/lib/
#18 0x00006453bb558bc5 in PyEval_
from /usr/lib/
#19 0x00006453bb55da75 in PyEval_EvalFrameEx ()
from /usr/lib/
#20 0x00006453bb560aae in PyEval_EvalCodeEx ()
from /usr/lib/
#21 0x00006453bb560b15 in PyEval_EvalCode () from /usr/lib/
#22 0x00006453bb56d6d0 in PyImport_
from /usr/lib/
#23 0x00006453bb56dade in ?? () from /usr/lib/
#24 0x00006453bb56e2f9 in ?? () from /usr/lib/
#25 0x00006453bb56e739 in ?? () from /usr/lib/
#26 0x00006453bb56f099 in PyImport_
from /usr/lib/
#27 0x00006453bb557530 in ?? () from /usr/lib/
#28 0x00006453bb4e8654 in PyObject_Call () from /usr/lib/
#29 0x00006453bb558bc5 in PyEval_
from /usr/lib/
#30 0x00006453bb55da75 in PyEval_EvalFrameEx ()
from /usr/lib/
#31 0x00006453bb560aae in PyEval_EvalCodeEx ()
from /usr/lib/
#32 0x00006453bb560b15 in PyEval_EvalCode () from /usr/lib/
#33 0x00006453bb56d6d0 in PyImport_
from /usr/lib/
#34 0x00006453bb56dade in ?? () from /usr/lib/
#35 0x00006453bb56e2f9 in ?? () from /usr/lib/
#36 0x00006453bb56e739 in ?? () from /usr/lib/
#37 0x00006453bb56f099 in PyImport_
from /usr/lib/
#38 0x00006453bb557530 in ?? () from /usr/lib/
#39 0x00006453bb4e8654 in PyObject_Call () from /usr/lib/
#40 0x00006453bb558bc5 in PyEval_
from /usr/lib/
#41 0x00006453bb55da75 in PyEval_EvalFrameEx ()
from /usr/lib/
#42 0x00006453bb560aae in PyEval_EvalCodeEx ()
from /usr/lib/
#43 0x00006453bb560b15 in PyEval_EvalCode () from /usr/lib/
#44 0x00006453bb56d6d0 in PyImport_
from /usr/lib/
#45 0x00006453bb56dade in ?? () from /usr/lib/
#46 0x00006453bb56e2f9 in ?? () from /usr/lib/
#47 0x00006453bb56e739 in ?? () from /usr/lib/
#48 0x00006453bb56f099 in PyImport_
from /usr/lib/
#49 0x00006453bb557530 in ?? () from /usr/lib/
#50 0x00006453bb4e8654 in PyObject_Call () from /usr/lib/
#51 0x00006453bb558bc5 in PyEval_
from /usr/lib/
Looks like this was already resolved in the bugreport you mentioned.
I am closing this as "invalid" because it's unlikely we can do anything about it and it was already fixed on the distro side.