Keepalived config is not future-proof

Bug #1814064 reported by Luis Filipe Domingues on 2019-01-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Luis Filipe Domingues

Bug Description

While doing some tests on one of our labs, we back-ported keepalived from disco (2.0.10). Doing that, keepalived stopped working.

The bug appear because keepalived, from version 2, switched from system() for executing scripts to execve().

The two jobs, vrrp_script haproxy_check_script and vrrp_script pingable_check_script, failed because the command is not executed in a shell anymore, and fail because the shell part (passed to the command as argument) are not understood by the command itself.

It could be a good idea to prepare the keepalived config to be future-proof.

Changed in openstack-ansible:
assignee: nobody → Luis Filipe Domingues (domigues-luis)
description: updated

Fix proposed to branch: master

Changed in openstack-ansible:
status: New → In Progress

Submitter: Zuul
Branch: master

commit f91b88078a71525608664df6b4559cd7908117b2
Author: Domingues Luis Filipe <email address hidden>
Date: Thu Jan 31 13:02:32 2019 +0100

    Make keepalived configuration future-proof

    As keepalived, from v2.0.0, uses execev() instead
    of system() for running scripts, the haproxy_check
    and the pingable_check will fail when upgrading
    keepalived. Exporting the full command into scripts
    make them compatibale with newer version of keepalived.

    Change-Id: Iea7d4565910046149d64dd1b4d8ec7bebb6e9e2a
    Closes-bug: #1814064

Changed in openstack-ansible:
status: In Progress → Fix Released

This issue was fixed in the openstack/openstack-ansible development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers