keepalived kolla_internal_vip_address no netmask

Bug #1642934 reported by Sascha Spreitzer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Won't Fix
Undecided
Unassigned

Bug Description

kolla-ansible has no distinguish way to setup netmask for kolla_internal_vip_address in keepalived.
If adding netmask, haproxy part fails.

Proposing to add kolla_internal_vip_netmask parameter which defaults to "32" to add netmask capability.

affects: kolla → kolla-ansible
Changed in kolla-ansible:
milestone: none → ocata-2
Changed in kolla-ansible:
milestone: ocata-2 → ocata-3
Changed in kolla-ansible:
milestone: ocata-3 → ocata-rc1
Changed in kolla-ansible:
milestone: ocata-rc1 → ocata-rc2
milestone: ocata-rc2 → pike-1
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

normally, keepalived use a /32.

you interface should have another address to use proper netmask. like

/24?

mark this as won't fix.

Changed in kolla-ansible:
status: New → Won't Fix
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.