Hide Forgot
Description of problem: Currently in the docs when we create the resource that need to run on the compute nodes we do not set the timeout to 200s like we do for the systemd resources as deployed on the controller. (The reason for 200s is to give enough time to systemd to forcibly stop a service without us recurring to fencing) So from the documentation: https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/high-availability-for-compute-instances/chapter-3-installation Section 13. heat-admin@controller-1 # sudo pcs resource create neutron-openvswitch-agent-compute systemd:neutron-openvswitch-agent --clone interleave=true --disabled --force Section 13.a heat-admin@controller-1 # sudo pcs resource create libvirtd-compute systemd:libvirtd --clone interleave=true --disabled --force Section 13.b heat-admin@controller-1 # sudo pcs resource create ceilometer-compute systemd:openstack-ceilometer-compute --clone interleave=true --disabled --force Section 13.c heat-admin@controller-1 # sudo pcs resource create ceilometer-compute systemd:openstack-ceilometer-compute --clone interleave=true --disabled --force All the above commands need to add a "op start timeout 200s stop timeout 200s" parameter. So for example: sudo pcs resource create neutron-openvswitch-agent-compute systemd:neutron-openvswitch-agent op start timeout 200s stop timeout 200s --clone interleave=true --disabled --force
*** Bug 1383780 has been marked as a duplicate of this bug. ***
Thanks Michele, I updated the doc per your correction. The changes should be up in a few hours on the portal (for both OSP8 and OSP9 versions of the doc).
Question what is the command to modify and the existing services? i.e. Rabbit?
answered my own question pcs resource update rabbitmq op add stop timeout=200s it needs the equal "="
On our weekly call, 11/10, we discussed this one and Mike O mentioned it should be more than a doc just that the script should be modified as well.
Clarification from Mike O: Correct. I think I probably worded it poorly on the call. I believe the intent here is the confirm that the docs on manual setup have been updated correctly & then make sure that the JS scripts that implement instance HA are updated accordingly. Apologies if that was confusing on the call.
Changes were published with OSP10 GA: https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/single/high-availability-for-compute-instances Setting to VERIFIED. If any further changes are required, please re-set to ASSIGNED and advise what needs to be changed.
LGTM, I guess we can close this one out?