Bug 1638350

Summary: overcloud deployment received 504 Gateway Time-out from mistral
Product: Red Hat OpenStack Reporter: Brad P. Crochet <brad>
Component: openstack-mistralAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: mlammon
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: abishop, agurenko, brad, gkadam, jjoyce, jlibosva, jschluet, jslagle, jtaleric, lmarsh, mbarnett, mburns, mcornea, mlammon, nlevinki, ohochman, rbrady, rhos-maint, shdunne, slinaber, therve, tvignaud, yprokule
Target Milestone: z3Keywords: Reopened, Triaged, ZStream
Target Release: 13.0 (Queens)Flags: mlammon: needinfo-
mlammon: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-mistral-6.0.5-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1628319 Environment:
Last Closed: 2018-11-27 12:50:56 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:

Comment 1 Brad P. Crochet 2018-10-15 12:32:15 UTC
*** Bug 1638474 has been marked as a duplicate of this bug. ***

Comment 2 Jon Schlueter 2018-10-16 18:17:39 UTC
Looks to be clean backport of upstream fix in LP https://bugs.launchpad.net/bugs/1789680

moving bug to POST

Comment 3 Jon Schlueter 2018-10-16 18:29:46 UTC
openstack-mistral-6.0.5-1.el7ost has this mentioned patch.

Comment 12 mlammon 2018-10-31 16:38:24 UTC
Installed latest puddle, register and introspect
(undercloud) [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed
13   -p 2018-10-24.1

Steps to Reproduce:
1. deploy undercloud, 
2. upload images
3. introspect nodes, tagging
4. prepare overcloud , etc

** wait **
(undercloud) [stack@undercloud-0 ~]$ uptime
 12:09:03 up 1 day, 21:28,  1 user,  load average: 0.99, 0.79, 0.67

deploy successfully!


2018-10-31 15:37:43Z [overcloud.AllNodesDeploySteps.CephStoragePostConfig]: CREATE_COMPLETE  state changed
2018-10-31 15:37:43Z [overcloud.AllNodesDeploySteps]: CREATE_COMPLETE  Stack CREATE completed successfully
2018-10-31 15:37:44Z [overcloud.AllNodesDeploySteps]: CREATE_COMPLETE  state changed
2018-10-31 15:37:44Z [overcloud]: CREATE_COMPLETE  Stack CREATE completed successfully

 Stack overcloud CREATE_COMPLETE

Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: 06251521-7b05-45fd-b415-298c03d08cd3
Overcloud Endpoint: http://10.0.0.105:5000/
Overcloud Horizon Dashboard URL: http://10.0.0.105:80/dashboard
Overcloud rc file: /home/stack/overcloudrc
Overcloud Deployed
(undercloud) [stack@undercloud-0 ~]$ uptime
 12:09:03 up 1 day, 21:28,  1 user,  load average: 0.99, 0.79, 0.67
(undercloud) [stack@undercloud-0 ~]$ openstack server list
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| ID                                   | Name         | Status | Networks               | Image          | Flavor     |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| 0c0bb205-73de-461e-a1d5-9fddf4d69e9a | controller-0 | ACTIVE | ctlplane=192.168.24.7  | overcloud-full | controller |
| bc243cfc-e3c7-46e7-80b4-e55b31df661e | controller-1 | ACTIVE | ctlplane=192.168.24.8  | overcloud-full | controller |
| ec70da97-9ad2-4fe0-9144-c1cb7d1561ec | compute-0    | ACTIVE | ctlplane=192.168.24.6  | overcloud-full | compute    |
| df5f7608-9483-41b2-8913-e42edbfe6fb2 | controller-2 | ACTIVE | ctlplane=192.168.24.22 | overcloud-full | controller |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+

Comment 15 errata-xmlrpc 2018-11-13 22:29:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3587