← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1779277] [NEW] nova-conductor problem with SSL handshake

 

Public bug reported:

After migration from Ocata to Pike I see some problems with nova-
conductor.

When I try to migrate a host, I get an error:

2018-06-29 10:24:42.546 811 WARNING keystoneauth.identity.generic.base [req-cc32cfb6-48ff-4803-bcea-96758514459c 5f620a8543154df1930316a7bf15f47e bd582a2363584a868a2966f1c4a1e56c - default default] Failed to discover available identity ve
rsions when contacting https://controller:35357/v3. Attempting to parse version from URL.: SSLError: SSL exception connecting to https://controller:35357/v3: ("bad handshake: Error([('', 'osrandom_rand_bytes', 'getrandom() initialization failed.')],)",)


After service restart - everything is OK.

Conductor is installed in VM with running haveged.

Looks like service is failing after long time being unused.

env:

Pike @ Ubuntu Xenial
nova-conductor: 2:16.1.0-0ubuntu1~cloud0

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1779277

Title:
  nova-conductor problem with SSL handshake

Status in OpenStack Compute (nova):
  New

Bug description:
  After migration from Ocata to Pike I see some problems with nova-
  conductor.

  When I try to migrate a host, I get an error:

  2018-06-29 10:24:42.546 811 WARNING keystoneauth.identity.generic.base [req-cc32cfb6-48ff-4803-bcea-96758514459c 5f620a8543154df1930316a7bf15f47e bd582a2363584a868a2966f1c4a1e56c - default default] Failed to discover available identity ve
  rsions when contacting https://controller:35357/v3. Attempting to parse version from URL.: SSLError: SSL exception connecting to https://controller:35357/v3: ("bad handshake: Error([('', 'osrandom_rand_bytes', 'getrandom() initialization failed.')],)",)

  
  After service restart - everything is OK.

  Conductor is installed in VM with running haveged.

  Looks like service is failing after long time being unused.

  env:

  Pike @ Ubuntu Xenial
  nova-conductor: 2:16.1.0-0ubuntu1~cloud0

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1779277/+subscriptions


Follow ups