keepalived 1.3.5 crashed in neutron-l3-agent when enabled router ha

Bug #1722505 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Unassigned

Bug Description

env:
centos 7.4 + kolla ocata image

centos 7.4 ship keepalived 1.3.5, which will raise segment fault when ip_vs module can not be loaded. keepalived related bug[0], and fix[1][2]

in ocata, neutron-l3-agent do not mount /lib/modules which case it load ip_vs failed and trigger this bug.

since pike, neutron-l3-agent mount /lib/modules, so it works as expect.

So we only need fix this issue on Ocata branch

[0] https://github.com/acassen/keepalived/issues/558
[1] https://github.com/acassen/keepalived/commit/dac727e1a7b676b38795d29909fb0658ed13fe17

Changed in kolla-ansible:
milestone: none → 4.0.3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/510834

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/ocata)

Reviewed: https://review.openstack.org/510834
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=5c42eee20925504e42764075449575c6040e3e74
Submitter: Jenkins
Branch: stable/ocata

commit 5c42eee20925504e42764075449575c6040e3e74
Author: Jeffrey Zhang <email address hidden>
Date: Tue Oct 10 18:49:33 2017 +0800

    Mount /lib/modules folder for neutron-l3-agent

    CentOS 7.4 ships keepalived 1.3.5, which raises segment fault if it can
    not load ip_vs module. This is a keepalived bug and 1.3.6 fixed this
    issue. Mount /lib/modules for neutron-l3-agent to avoid this issue.

    Since this folder is mounted since Pike branch, so this bug only affacts
    Ocata branch.

    Change-Id: I0b1392284de54df3d4d7477c3b513529c809b9fe
    Closes-Bug: #1722505

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 4.0.3

This issue was fixed in the openstack/kolla-ansible 4.0.3 release.

Changed in kolla-ansible:
milestone: 4.0.3 → 4.0.4
Changed in kolla-ansible:
milestone: 4.0.4 → 4.0.5
Changed in kolla-ansible:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.