yahoo-eng-team team mailing list archive

[Lee Yarwood <lyarwood@xxxxxxxxxx>]

Public bug reported:

Description
===========

$ cat /etc/redhat-release 
Fedora release 25 (Twenty Five)
$ /usr/bin/nova-manage --config-file /etc/nova/nova.conf api_db sync
Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:16> ignored
Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:17> ignored
Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:10> ignored
Traceback (most recent call last):
  File "/usr/bin/nova-manage", line 6, in <module>
    from nova.cmd.manage import main
  File "/opt/stack/nova/nova/cmd/manage.py", line 65, in <module>
    from oslo_db import exception as db_exc
  File "/usr/lib/python2.7/site-packages/oslo_db/exception.py", line 50, in <module>
    from oslo_utils.excutils import CausedByException
  File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 32, in <module>
    from oslo_utils import timeutils
  File "/usr/lib/python2.7/site-packages/oslo_utils/timeutils.py", line 27, in <module>
    from monotonic import monotonic as now  # noqa
  File "/usr/lib/python2.7/site-packages/monotonic.py", line 169, in <module>
    raise RuntimeError('no suitable implementation for this system')
RuntimeError: no suitable implementation for this system

Skipping ahead and directly importing oslo_db.exception doesn't produce
the same trace :

$ python
Python 2.7.13 (default, Jan 12 2017, 17:59:37) 
[GCC 6.3.1 20161221 (Red Hat 6.3.1-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from oslo_db import exception as db_exc
>>> db_exc
<module 'oslo_db.exception' from '/usr/lib/python2.7/site-packages/oslo_db/exception.pyc'>

Steps to reproduce
==================
As above.

Expected result
===============
api_db sync completes.

Actual result
=============
api_db sync fails with the above trace.

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

$ git log -1
commit 221427a0439567681a5980dee5412aefc87d674d
Merge: c66774f 14732e5
Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
Date:   Mon May 15 10:40:37 2017 +0000

  Merge "Add uuid to service.update notification payload"

2. Which hypervisor did you use?
 
  F25, libvirt + KVM

2. Which storage type did you use?
  
  N/A

3. Which networking type did you use?

  N/A

Logs & Configs
==============
  Provided above.

** 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/1690819

Title:
  nova-manage [..] api_db sync on F25 results in RuntimeError: no
  suitable implementation for this system

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========

  $ cat /etc/redhat-release 
  Fedora release 25 (Twenty Five)
  $ /usr/bin/nova-manage --config-file /etc/nova/nova.conf api_db sync
  Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:16> ignored
  Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:17> ignored
  Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:10> ignored
  Traceback (most recent call last):
    File "/usr/bin/nova-manage", line 6, in <module>
      from nova.cmd.manage import main
    File "/opt/stack/nova/nova/cmd/manage.py", line 65, in <module>
      from oslo_db import exception as db_exc
    File "/usr/lib/python2.7/site-packages/oslo_db/exception.py", line 50, in <module>
      from oslo_utils.excutils import CausedByException
    File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 32, in <module>
      from oslo_utils import timeutils
    File "/usr/lib/python2.7/site-packages/oslo_utils/timeutils.py", line 27, in <module>
      from monotonic import monotonic as now  # noqa
    File "/usr/lib/python2.7/site-packages/monotonic.py", line 169, in <module>
      raise RuntimeError('no suitable implementation for this system')
  RuntimeError: no suitable implementation for this system

  Skipping ahead and directly importing oslo_db.exception doesn't
  produce the same trace :

  $ python
  Python 2.7.13 (default, Jan 12 2017, 17:59:37) 
  [GCC 6.3.1 20161221 (Red Hat 6.3.1-1)] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> from oslo_db import exception as db_exc
  >>> db_exc
  <module 'oslo_db.exception' from '/usr/lib/python2.7/site-packages/oslo_db/exception.pyc'>

  Steps to reproduce
  ==================
  As above.

  Expected result
  ===============
  api_db sync completes.

  Actual result
  =============
  api_db sync fails with the above trace.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

  $ git log -1
  commit 221427a0439567681a5980dee5412aefc87d674d
  Merge: c66774f 14732e5
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Mon May 15 10:40:37 2017 +0000

    Merge "Add uuid to service.update notification payload"

  2. Which hypervisor did you use?
   
    F25, libvirt + KVM

  2. Which storage type did you use?
    
    N/A

  3. Which networking type did you use?

    N/A

  Logs & Configs
  ==============
    Provided above.

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