Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1613948

Summary: FFWD: openstack overcloud upgrade run fails with FAILED! => {"changed": false, "msg": "async task did not complete within the requested time"}
Product: Red Hat OpenStack Reporter: Darin Sorrentino <dsorrent>
Component: python-tripleoclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED NOTABUG QA Contact: Gurenko Alex <agurenko>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: hbrock, jslagle, lbezdick, mburns, morazi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-08 17:55:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
package_update log from Mistral.
none
nova-manage.log from the node none

Description Darin Sorrentino 2018-08-08 15:35:52 UTC
Created attachment 1474389 [details]
package_update log from Mistral.

Description of problem:

During the upgrade run of the Overcloud, it failed with this error in the package_update.log.

Checking nova-manage on the node shows it can not connect to MySQL.  Manual attempt to run nova db sync has the same effect.

We can access mysql by executing the mysql command.

The previous step where it does the cell create and uses --database_connection switch succeeds.  We compared the hiera data used from that command to what is in /etc/nova/nova.conf and it matches.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Darin Sorrentino 2018-08-08 15:36:44 UTC
Created attachment 1474390 [details]
nova-manage.log from the node

Comment 4 Mike Orazi 2018-08-08 16:14:15 UTC
Further inspection seems to reveal that this is likely a typo in the Vip in tht.

Comment 5 Darin Sorrentino 2018-08-08 17:54:34 UTC
Issue looks to be related to a typo in the InternalAPI VIP between the 10->13 template creation. After correcting it in the 13 templates, re-executing the prepare and run completed successfully.

Comment 6 Darin Sorrentino 2018-08-08 17:55:11 UTC
Closing.