Ocata -> Pike undercloud upgrade fails: Reason: object.__new__(thread.lock) is not safe, use thread.lock.__new__()

Bug #1693790 reported by Marius Cornea
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Unassigned

Bug Description

Ocata -> Pike undercloud upgrade fails with the following error message:

#############################################################################
Undercloud upgrade 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.

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

The upgrade process though seems to reach the last steps. Attaching the install-undercloud.log

Overcloud nova nodes are in error state after upgrade:

(undercloud) [stack@undercloud-0 ~]$ nova list
+--------------------------------------+------------------------+--------+------------+-------------+-----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------------------------+--------+------------+-------------+-----------------------+
| d3f92a37-2b6b-4370-8430-3f1ffbb4994e | overcloud-controller-0 | ERROR | - | Running | ctlplane=192.168.0.19 |
+--------------------------------------+------------------------+--------+------------+-------------+-----------------------+

Reproducing steps:
1. Depoy Ocata undercloud and overcloud
2. Upgrade undercloud per the instructions at https://docs.openstack.org/developer/tripleo-docs/post_deployment/upgrade.html

Tags: upgrade
Revision history for this message
Marius Cornea (mcornea) wrote :
Marius Cornea (mcornea)
Changed in tripleo:
status: New → Triaged
Changed in tripleo:
milestone: pike-2 → pike-3
Revision history for this message
Marios Andreou (marios-b) wrote :
Changed in tripleo:
milestone: pike-3 → pike-rc1
Revision history for this message
Ben Nemec (bnemec) wrote :

Agree with Marios, and marking as a duplicate since the other bug is already tracked for tripleo too.

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.