Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1285363 - Deployment failure "httpd never started after 200 seconds"
Deployment failure "httpd never started after 200 seconds"
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity unspecified
: y2
: 7.0 (Kilo)
Assigned To: Jiri Stransky
Alexander Chuzhoy
:
: 1284121 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-25 08:15 EST by Jiri Stransky
Modified: 2015-12-21 11:53 EST (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-0.8.6-85.el7ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-21 11:53:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 249716 None None None Never
Red Hat Product Errata RHSA-2015:2650 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Linux OpenStack Platform 7 director update 2015-12-21 16:44:54 EST

  None (edit)
Description Jiri Stransky 2015-11-25 08:15:05 EST
A deployment failed with this message in os-collect-config log:

Nov 24 18:09:38 overcloud-controller-0.localdomain 
os-collect-config[2921]: httpd not yet started, sleeping 3 seconds.
Nov 24 18:09:38 overcloud-controller-0.localdomain 
os-collect-config[2921]: httpd not yet started, sleeping 3 seconds.
Nov 24 18:09:38 overcloud-controller-0.localdomain 
os-collect-config[2921]: httpd never started after 200 seconds

However, when the environment was investigated, all services were already up and running.

[root@overcloud-controller-0 ~]# pcs status | grep Stopped -C2
[root@overcloud-controller-0 ~]#

There were a few monitor action timeouts in pcmk, but no start/stop timeouts. The actual httpd start time on one of the controllers exceeded the timeout by about 10 seconds, causing the deployment to fail:

Nov 24 18:09:31 overcloud-controller-0.localdomain crmd[29936]: notice: 
Operation httpd_start_0: ok (node=overcloud-controller-0, call=430, 
rc=0, cib-update=246, confirmed=true)

Nov 24 18:09:49 overcloud-controller-1.localdomain crmd[29784]: notice: 
Operation httpd_start_0: ok (node=overcloud-controller-1, call=425, 
rc=0, cib-update=403, confirmed=true)

^^ this one timed out

Nov 24 18:09:07 overcloud-controller-2.localdomain crmd[29500]: notice: 
Operation httpd_start_0: ok (node=overcloud-controller-2, call=422, 
rc=0, cib-update=270, confirmed=true)


The current timeout values are probably too aggressive for slow virtualized environments, and should be bumped up.
Comment 1 Jiri Stransky 2015-11-25 11:50:01 EST
*** Bug 1284121 has been marked as a duplicate of this bug. ***
Comment 4 Alexander Chuzhoy 2015-12-03 11:07:41 EST
Verified:

Environment:
openstack-tripleo-heat-templates-0.8.6-85.el7ost.noarch


The reported issue doesn't reproduce. Able to deploy HA.
Comment 8 errata-xmlrpc 2015-12-21 11:53:00 EST
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/RHSA-2015:2650

Note You need to log in before you can comment on or make changes to this bug.