| Summary: | Can't re-launch horizon after a controller reboot: ImportError: cannot import name base | ||
|---|---|---|---|
| Product: | [Community] RDO | Reporter: | Udi Kalifon <ukalifon> |
| Component: | python-cinderclient | Assignee: | Eric Harney <eharney> |
| Status: | CLOSED EOL | QA Contact: | nlevinki <nlevinki> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | aortega, athomas, eharney, mrunge, srevivo |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | Kilo | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-19 15:55:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Udi Kalifon
2016-02-02 14:42:51 UTC
This looks suspicious here, after Horizon, there is cinderclient, then eventlet and OpenSSL involved. I could not reproduce this in tests, thus it might be timing related, which makes a bit of sense, after working fine before reboot. The error is thrown in python-cryptography itself. Udi, would it be possible to reboot again? I rebooted again and horizon came up right this time. There seems to be a timing issue in the whole stack. Not really sure, who to blame in the long queue.
File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 95, in _ensure_ffi_initialized
cls._register_osrandom_engine()
File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 70, in _register_osrandom_engine
raise RuntimeError("osrandom engine already registered")
RuntimeError: osrandom engine already registered
states, python-cryptography had the issue, re-adjusting to python-cinderclient, as that was the last RDO component causing this issue.
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen. |