Locking of conductor service process during DNS name resolving retries

Bug #1686675 reported by Yuriy Zveryanskyy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Triaged
High
Unassigned

Bug Description

For pure Python drivers (like iLO) vendor's library should resolve host names of management controllers (if they are used instead of IP's). Conductor service process can do this resolving frequently if local cache is not used. We set EVENTLET_NO_GREENDNS env variable for eventlet, and locking on one greenthread is possible on retries if DNS server temporary is not accessible. Typical retries time is 10 second (see man resolv.conf for detail). Eventlet resolver for older version does not support IPV6 at all, for current requirements a bug with IPV6 documented. We should switch ironic to "green" resolving in the future (versions in the requirements should not contain documented DNS resolving bugs).

Tags: conductor
Dmitry Tantsur (divius)
Changed in ironic:
status: New → Triaged
importance: Undecided → High
tags: added: conductor
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.