Marking as wont-fix for cloud-init for now as that would be a workaround
for the base problem that is not desired right now. Adding linux-kvm to
evaluate why this difference exists between linux-generic and linux-kvm
** Changed in: cloud-init
Status: Incomplete => Won't Fix
** Also affect
I've tracked down the blocking use of randomness in cloud-init's python
module initialization. There are several nonblocking calls to
getrandom(), which I believe should be fine; then a blocking call in the
multiprocessing module.
# PYTHONHASHSEED=1 gdb --args /usr/bin/python3-dbg /usr/bin/cloud-
Could you run
cloud-init collect-logs
And then attach the cloud-init.tar.gz
Also, Can you provide some information on what you were running?
" cloud-init is slow to complete init on minimized images "
How can I recreate this?
One curious thing there is:
2017-10-25 13:22:07,157 - util.py[WARN
3 matches
Mail list logo
