[openstack-dashboard] apache service is not serving requests after run the dashboard cookbook recipes

Bug #1450267 reported by Terry Yao
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack + Chef
Invalid
Low
Unassigned

Bug Description

In our chef-client run list, I have some other recipes runs after the os-dashboard-node role, and after run the horizon cookbook, my recipes will fire some request for apache service after the horizon cookbook, but apache services can not response the request.

From the chef-client run log, there will be a apache service reload immediately called while run horizon cookbook, and there will also be a delay apache service restart after all recipes run over..

For the reproduce steps:
1. We have a recipe in the run-list before the openstack-dashboard, and it's proxy the keystone port to apache http port:
and it will restart the httpd after configure the proxy template immediately
2. Then the run-list will call openstack-dashboard cookbook' recipe
3. In our run-list, we have another recipe will call keystone command, then it fails to communicate with keystone port that is proxied configured in step #1, and it gets hang as openstack-dashboard is not fully restarted, the proxied http port can not be connected from a client.

Tags: dashboard
Revision history for this message
Mark Vanderwiel (vanderwl) wrote :

Would like to see more info on how to reproduce this. This might be a better bug for the apache2 cookbook itself.

tags: added: dashboard
Changed in openstack-chef:
status: New → Incomplete
Revision history for this message
Terry Yao (yaohaif) wrote :

For the reproduce steps:
1. We have a recipe in the run-list before the openstack-dashboard, and it's proxy the keystone port to apache http port:
and it will restart the httpd after configure the proxy template immediately
2. Then the run-list will call openstack-dashboard cookbook' recipe
3. In our run-list, we have another recipe will call keystone command, then it fails to communicate with keystone port that is proxied configured in step #1, and it gets hang as openstack-dashboard is not fully restarted, the proxied http port can not be connected from a client.

description: updated
Changed in openstack-chef:
status: Incomplete → Triaged
Revision history for this message
Mark Vanderwiel (vanderwl) wrote :

I think this will be fixed with the keystone under apache patches: https://review.openstack.org/#/q/status:open++branch:master+topic:bp/keystone-apache,n,z
Please confirm, thx.

Changed in openstack-chef:
milestone: none → liberity-rc1
importance: Undecided → Low
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Please check if the issue still exists with the current state of the cookbooks for Newton.

Changed in openstack-chef:
status: Triaged → Incomplete
Changed in openstack-chef:
status: Incomplete → Invalid
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.