undercloud install failed due to TypeError thread.lock

Bug #1687867 reported by nate
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

I am following the installation instructions at: http://tripleo.org/installation/installation.html

I chose the ocata release. The OS is a fresh install and fully updated version of CentOS 7 in a KVM virtual machine. The goal is to get the undercloud running in a virt to manage a overcloud of 3 physical machines.

I blew away the VM the first time I ran into this and tried it again and had the same results. Appears to be a conflict with some python version or something like that. I don't know where to begin looking.

As far as the commands I ran I just copied and pasted them from the installation instructions, choosing the ocata curl commands for setting up the repositories.

This is the message I get with the install at the end of /home/stack/.instack/install-undercloud.log

2017-05-03 02:26:30,754 DEBUG: POST call to compute for http://10.0.0.4:8774/v2.1/flavors/8fe1d5ff-9f65-447e-b19d-da1ca809b538/os-extra_specs used request id req-114cb090-98d3-4353-920d-4cdc67b6bdca
2017-05-03 02:26:30,755 INFO: Created flavor "swift-storage" with profile "swift-storage"
2017-05-03 02:26:30,755 ERROR:
#############################################################################
Undercloud install failed.

Reason: object.__new__(thread.lock) is not safe, use thread.lock.__new__()

See the previous output for details about what went wrong. The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Here what I saw in the command line output from 'openstack undercloud install'

2017-05-03 02:26:30,588 INFO: Created flavor "ceph-storage" with profile "ceph-storage"
2017-05-03 02:26:30,671 INFO: Created flavor "block-storage" with profile "block-storage"
2017-05-03 02:26:30,755 INFO: Created flavor "swift-storage" with profile "swift-storage"
2017-05-03 02:26:30,755 ERROR:
#############################################################################
Undercloud install failed.

Reason: object.__new__(thread.lock) is not safe, use thread.lock.__new__()

See the previous output for details about what went wrong. The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1529, in install
    _post_config(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1454, in _post_config
    session=sess)
  File "/usr/lib/python2.7/site-packages/mistralclient/api/client.py", line 19, in client
    return client_v2.Client(auth_type=auth_type, **kwargs)
  File "/usr/lib/python2.7/site-packages/mistralclient/api/v2/client.py", line 42, in __init__
    req = copy.deepcopy(kwargs)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 334, in _reconstruct
    state = deepcopy(state, memo)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 334, in _reconstruct
    state = deepcopy(state, memo)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 329, in _reconstruct
    y = callable(*args)
  File "/usr/lib64/python2.7/copy_reg.py", line 93, in __newobj__
    return cls.__new__(cls, *args)
TypeError: object.__new__(thread.lock) is not safe, use thread.lock.__new__()
Command 'instack-install-undercloud' returned non-zero exit status 1

Here is my undercloud.conf:

[DEFAULT]
undercloud_hostname = undercloud.example.com
local_interface = eth1
local_ip = 10.0.0.4/16
network_gateway = 10.0.0.4
undercloud_nameservers = 192.168.1.1
undercloud_ntp_servers = 0.fedora.pool.ntp.org, 1.fedora.pool.ntp.org, 2.fedora.pool.ntp.org
local_mtu = 1500
network_cidr = 10.0.0.20/16
masquerade_network = 10.0.0.20/16
dhcp_start = 10.0.0.5
dhcp_end = 10.0.0.25
inspection_iprange = 10.0.0.26,10.0.0.37
discovery_iprange = 10.0.0.26,10.0.0.37
enable_node_discovery = true
undercloud_debug = true
undercloud_update_packages = true
enable_tempest = true
enable_ui = true
enable_cinder = false
clean_nodes = true
# http://blog.leifmadsen.com/blog/2016/11/11/tripleo-using-the-fake_pxe-driver-with-ironic/
enabled_drivers = pxe_ipmitool,pxe_ssh,pxe_drac,pxe_ilo,fake_pxe
[auth]

Revision history for this message
mayuran sub (msswdev) wrote :

I'm also running into the same issue/error.
I had successfully deployed an TripleO Undercloud Node about 1 weeks ago.
Now, I'm trying to install the undercloud on a different node and it fails with above error.
Looks like some code have changed within the last week.

PS: I'm installing undercloud on a baremetal node.

ERRORS:
===========
2017-05-03 15:16:17,448 INFO: Created flavor "swift-storage" with profile "swift-storage"
2017-05-03 15:16:17,449 ERROR:
#############################################################################
Undercloud install failed.

Reason: object.__new__(thread.lock) is not safe, use thread.lock.__new__()

See the previous output for details about what went wrong. The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1529, in install
    _post_config(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1454, in _post_config
    session=sess)
  File "/usr/lib/python2.7/site-packages/mistralclient/api/client.py", line 19, in client
    return client_v2.Client(auth_type=auth_type, **kwargs)
  File "/usr/lib/python2.7/site-packages/mistralclient/api/v2/client.py", line 42, in __init__
    req = copy.deepcopy(kwargs)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 334, in _reconstruct
    state = deepcopy(state, memo)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 334, in _reconstruct
    state = deepcopy(state, memo)
  File "/usr/lib64/python2.7/copy.py", line 163, in deepcopy
    y = copier(x, memo)
  File "/usr/lib64/python2.7/copy.py", line 257, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/usr/lib64/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/lib64/python2.7/copy.py", line 329, in _reconstruct
    y = callable(*args)
  File "/usr/lib64/python2.7/copy_reg.py", line 93, in __newobj__
    return cls.__new__(cls, *args)
TypeError: object.__new__(thread.lock) is not safe, use thread.lock.__new__()
Command 'instack-install-undercloud' returned non-zero exit status 1
===========

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-2
Revision history for this message
mayuran sub (msswdev) wrote :

Update:

I deployed tripleO with the attached list of repos (1 or 2 weeks old) and without using source.

i.e: not running "export DIB_INSTALLTYPE_puppet_modules=source".

Hope this may help someone.

Revision history for this message
Yusuf Hadiwinata (yusuf-hadiwinata) wrote :
Download full text (4.6 KiB)

Got same problem

2017-05-20 04:00:11,584 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 99-refresh-completed completed
2017-05-20 04:00:11,585 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 ----------------------- PROFILING -----------------------
2017-05-20 04:00:11,586 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017
2017-05-20 04:00:11,588 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 Target: post-configure.d
2017-05-20 04:00:11,589 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017
2017-05-20 04:00:11,590 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 Script Seconds
2017-05-20 04:00:11,590 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 --------------------------------------- ----------
2017-05-20 04:00:11,591 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017
2017-05-20 04:00:11,596 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 10-iptables 0.004
2017-05-20 04:00:11,600 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 80-seedstack-masquerade 0.018
2017-05-20 04:00:11,604 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 98-undercloud-setup 160.270
2017-05-20 04:00:11,607 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 99-refresh-completed 0.887
2017-05-20 04:00:11,609 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017
2017-05-20 04:00:11,610 INFO: dib-run-parts Sat May 20 04:00:11 WIB 2017 --------------------- END PROFILING ---------------------
2017-05-20 04:00:11,610 INFO: [2017-05-20 04:00:11,610] (os-refresh-config) [INFO] Completed phase post-configure
2017-05-20 04:00:11,616 INFO: os-refresh-config completed successfully
2017-05-20 04:00:13,332 INFO: Not creating flavor "baremetal" because it already exists.
2017-05-20 04:00:13,374 INFO: Not creating flavor "control" because it already exists.
2017-05-20 04:00:13,416 INFO: Not creating flavor "compute" because it already exists.
2017-05-20 04:00:13,457 INFO: Not creating flavor "ceph-storage" because it already exists.
2017-05-20 04:00:13,499 INFO: Not creating flavor "block-storage" because it already exists.
2017-05-20 04:00:13,608 INFO: Not creating flavor "swift-storage" because it already exists.
2017-05-20 04:00:13,608 ERROR:
#############################################################################
Undercloud install failed.

Reason: object.__new__(thread.lock) is not safe, use thread.lock.__new__()

See the previous output for details about what went wrong. The full install
log can be found at /home/stack/.instack/install-undercloud.log.

#############################################################################

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1555, in install
    _post_config(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1480, in _post_config
    session=sess)
  File "/usr/lib/python2.7/site-packages/mistralclient/api/client.py", line 19, in client
    return client_v2.Client(auth_type=auth_type, **kwargs)
  File "/usr/lib/python2.7/site-packages/mi...

Read more...

Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
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.