kolla

keepalived config has erroneous priority calculation

Bug #1494237 reported by Vladislav Belogrudov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
Vladislav Belogrudov
kolla liberty-rc1 "liberty-rc1"

Bug Description

keepalived only accepts priority from 1 to 255. Ansible starts first keepalived container with priority 0. This gives error and keepalived resumes with default priority 100

Vladislav Belogrudov (vlad-belogrudov)
Changed in kolla:
importance: Undecided → High
assignee: nobody → Vladislav Belogrudov (vlad-belogrudov)
milestone: none → liberty-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/222116

Changed in kolla:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/222116
Committed: https://git.openstack.org/cgit/stackforge/kolla/commit/?id=9d156eb005608fa822ff049a4cbd19890fd102f5
Submitter: Jenkins
Branch: master

commit 9d156eb005608fa822ff049a4cbd19890fd102f5
Author: Vladislav Belogrudov <email address hidden>
Date: Thu Sep 10 13:22:00 2015 +0300

    First keepalived container is started with wrong priority

    First keepalived container is started with priority 0 but the
    latter should be in range 1-255. This gives error and keepalived
    resumes with default priority 100.

    Change-Id: Ib11d0072a96b818d86c81a32e78118c0c82b74d8
    Closes-Bug: #1494237

Changed in kolla:
status: In Progress → Fix Committed
Sam Yaple (s8m)
Changed in kolla:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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