Red Hat Bugzilla – Bug 1262409
Remove start-delay=10s from the nova resources
Last modified: 2016-04-07 17:39:38 EDT
Description of problem: Currently on controllers the nova resources have a start-delay operation: Clone: openstack-nova-scheduler-clone Resource: openstack-nova-scheduler (class=systemd type=openstack-nova-scheduler) Operations: start interval=0s timeout=60s (openstack-nova-scheduler-start-timeout-60s) monitor interval=60s start-delay=10s (openstack-nova-scheduler-monitor-start-delay-10s) Clone: openstack-nova-api-clone Resource: openstack-nova-api (class=systemd type=openstack-nova-api) Operations: start interval=0s timeout=60s (openstack-nova-api-start-timeout-60s) monitor interval=60s start-delay=10s (openstack-nova-api-monitor-start-delay-10s) Clone: openstack-nova-consoleauth-clone Resource: openstack-nova-consoleauth (class=systemd type=openstack-nova-consoleauth) Operations: start interval=0s timeout=60s (openstack-nova-consoleauth-start-timeout-60s) monitor interval=60s start-delay=10s (openstack-nova-consoleauth-monitor-start-delay-10s) Clone: openstack-nova-novncproxy-clone Resource: openstack-nova-novncproxy (class=systemd type=openstack-nova-novncproxy) Operations: start interval=0s timeout=60s (openstack-nova-novncproxy-start-timeout-60s) monitor interval=60s start-delay=10s (openstack-nova-novncproxy-monitor-start-delay-10s) Clone: openstack-nova-conductor-clone Resource: openstack-nova-conductor (class=systemd type=openstack-nova-conductor) Operations: start interval=0s timeout=60s (openstack-nova-conductor-start-timeout-60s) monitor interval=60s start-delay=10s (openstack-nova-conductor-monitor-start-delay-10s) I spoke to Giulio about this and it seems this was taken as is from here: https://github.com/redhat-openstack/astapor/blob/08aea96e75b7a2000e17b3172b05bb8950702727/puppet/modules/quickstack/manifests/pacemaker/nova.pp#L130 This was subsequently removed in that repo as well, but it remained in osp-d. Since this start-delay is also not present in the osp-ha refarch (https://github.com/beekhof/osp-ha-deploy/blob/master/ha-openstack.md), best if we kill this start-delay thing.
Verified as follows, ***** File ***** [stack@undercloud ~]$ sudo rpm -qa openstack-tripleo-heat-templates openstack-tripleo-heat-templates-0.8.8-2.el7ost.noarch [stack@undercloud ~]$ /usr/share/openstack-tripleo-heat-templates/puppet/manifests/overcloud_controller_pacemaker.pp ***** Logs ***** # Nova pacemaker::resource::service { $::nova::params::api_service_name : clone_params => 'interleave=true', } pacemaker::resource::service { $::nova::params::conductor_service_name : clone_params => 'interleave=true', } pacemaker::resource::service { $::nova::params::consoleauth_service_name : clone_params => 'interleave=true', require => Pacemaker::Resource::Service[$::keystone::params::service_name], } pacemaker::resource::service { $::nova::params::vncproxy_service_name : clone_params => 'interleave=true', } pacemaker::resource::service { $::nova::params::scheduler_service_name : clone_params => 'interleave=true', }
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://rhn.redhat.com/errata/RHEA-2016-0604.html