Red Hat Bugzilla – Bug 1251322
op start timeout too short for httpd pacemaker resource
Last modified: 2016-05-20 11:09:20 EDT
With a Staypuft deployed Pacemaker configuration, we have: # pcs resource show horizon-clone Clone: horizon-clone Meta Attrs: interleave=true Resource: horizon (class=systemd type=httpd) Attributes: start-delay=10s Operations: monitor interval=60s (horizon-monitor-interval-60s) That 10s start-delay can be too short given the pre-startup processes we run in /lib/systemd/system/httpd.service.d/openstack-dashboard.conf. I think we should crank this up to 60s.
So, s/start-delay/op start timeout/. I was able to get reliable resoure startup by running: pcs resource op add horizon start interval=0 timeout=120
Moving to rhel-osp-installer components since this is staypuft.
Adding Matthias to give guidance how long collectstatic + compress can take.
I would even give it a little more, depending on IO speed. This compress step runs through all css/sass/less files, parsing and translating them. On a slow machine, this still shouldn't take longer than 2 mins.
I don't believe any code fix will be made to adjust this at this point, reopen if it becomes a priority. Otherwise, I think this is a manual step if needed for anyone on legacy setup.