User Guide in OpenStack-Ansible has wrong IP address for haproxy_keepalived_internal_vip_cidr

Bug #1773793 reported by Niklas Hagman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Low
Dmitriy Rabotyagov

Bug Description

https://docs.openstack.org/openstack-ansible/latest/user/prod/example.html
https://docs.openstack.org/openstack-ansible/queens/user/prod/example.html
https://docs.openstack.org/openstack-ansible/latest/user/l3pods/example.html
https://docs.openstack.org/openstack-ansible/queens/user/l3pods/example.html
https://docs.openstack.org/openstack-ansible/latest/user/ceph/full-deploy.html
https://docs.openstack.org/openstack-ansible/queens/user/ceph/full-deploy.html

These pages has documentation saying haproxy_keepalived_internal_vip_cidr should be "172.29.236.0/22". But the examples configures 172.29.236.9 to be the internal vip address.

Documentation should say haproxy_keepalived_internal_vip_cidr: "172.29.236.9/22".

this also needs to be fixed in source code examples
--- openstack-ansible/etc/openstack_deploy/user_variables.yml.prod-ceph.example
+++ openstack-ansible.changes/etc/openstack_deploy/user_variables.yml.prod-ceph.example
@@ -6 +6 @@
-haproxy_keepalived_internal_vip_cidr: "172.29.236.0/22"
+haproxy_keepalived_internal_vip_cidr: "172.29.236.9/22"

--- openstack-ansible/etc/openstack_deploy/user_variables.yml.prod.example
+++ openstack-ansible.changes/etc/openstack_deploy/user_variables.yml.prod.example
@@ -7 +7 @@
-haproxy_keepalived_internal_vip_cidr: "172.29.236.0/22"
+haproxy_keepalived_internal_vip_cidr: "172.29.236.9/22"

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
tags: added: low-hanging-fruit
Ilya Popov (ilya-p)
Changed in openstack-ansible:
assignee: nobody → Ilya Popov (ilya-p)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)

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

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
Niklas Hagman (blinkiz) wrote :

I do think both these should be /32 and not /22.
A IPv4 with /22 is already defined on this bridge/interface. Creating another way out into this subnet is not the purpose.

Revision history for this message
Ilya Popov (ilya-p) wrote :

Agree. Checked in code:

1. There is a comment in user_variables.yml:

# haproxy_keepalived_internal_vip_cidr: "{{internal_lb_vip_address}}/32"

2. There is a ip check procedure which asserts ip in healthcheck-hosts.yml - ip should be host ip, not network ip

    - name: Checking that vip address is well formed
      assert:
        that:
          - item | ipaddr('address')
        msg: "Misconfigured keepalived: The vip {{ item }} is not an IP address, but a network"
      with_items:
        - "{{ haproxy_keepalived_internal_vip_cidr }}"
        - "{{ haproxy_keepalived_external_vip_cidr }}"
      when:
        - groups['haproxy_all'] | length > 1

Revision history for this message
Ilya Popov (ilya-p) wrote :

Fixed in new patchset

Changed in openstack-ansible:
assignee: Ilya Popov (ilya-p) → Dmitriy Rabotyagov (noonedeadpunk)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (master)

Reviewed: https://review.opendev.org/572935
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=cc1cb3ad370412b744005e8de2d7d08c23932be5
Submitter: Zuul
Branch: master

commit cc1cb3ad370412b744005e8de2d7d08c23932be5
Author: Ilya Popov <email address hidden>
Date: Wed Jun 6 22:30:09 2018 +0300

    IP addresses in examples were changed

    IP addresses in examples were changed from 172.29.236.0/22
    to 172.29.236.9/32 to be the same in all part of the document.

    Change-Id: I69bb78463dbe4f78ef266e8e98631a4e4af1cc28
    Closes-Bug: #1773793

Changed in openstack-ansible:
status: In Progress → 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.