StarlingX

  1. Bug #1886003
  2. Comment #5

Comment 5 for bug 1886003

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-armada-app (master)

Reviewed: https://review.opendev.org/739046
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=2496a170fea73385ddfbfe8d7187311df2f2f236
Submitter: Zuul
Branch: master

commit 2496a170fea73385ddfbfe8d7187311df2f2f236
Author: Zhipeng Liu <email address hidden>
Date: Fri Jul 3 06:38:33 2020 +0800

    Fix the second mariadb node could not join cluster issue.

    This bug was introduced by below commit
    d3164c63dc24e0a74cf001a1366cb92dd6a7e396
    The update after PATCH SET 10 will cause the second mariadb could not
    join cluster. In this case, could not set bind_address=:: for ipv4. It
    only works for ipv6.

    As for conf.database.config_override, we can override it through
    system helm-override-update command, but could not use python
    plugin to dynamically override it as it will introduce a "-|" line
    in first line of config file.
    A user override for conf.database.config_override might break the IPv6
    system overrides, it need including ipv6 config for ipv6 case as well.

    Test pass on duplex setup. Openstack application applied successfully.

    Closes-Bug: 1886003

    Change-Id: I23c2fb6a7c8b5a38af1e046894d5fae247df2d6f
    Signed-off-by: Zhipeng Liu <email address hidden>