masakari

  1. Bug #1873736
  2. Comment #18

Comment 18 for bug 1873736

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to masakari-monitors (stable/train)

Reviewed: https://review.opendev.org/752425
Committed: https://git.openstack.org/cgit/openstack/masakari-monitors/commit/?id=4d13e712cbb4139c6e04fe4a3b00a4072d195eb1
Submitter: Zuul
Branch: stable/train

commit 4d13e712cbb4139c6e04fe4a3b00a4072d195eb1
Author: Mark Goddard <email address hidden>
Date: Fri Jul 17 19:02:28 2020 +0000

    Use keystoneauth1 config option loading for masakari client

    If a custom CA file is configured via [api] cafile, currently
    communication with Keystone will fail, since the session is not created
    using this CA file. The [api] insecure option is also ignored.

    This change fixes the issue by using keystoneauth loading for the auth
    and session, to ensure all standard configuration options are supported.

    Change-Id: Idd58b72f7f5242e8135fec71b42adf5dd1852417
    Closes-Bug: #1873736
    (cherry picked from commit e70404588002222c8475667ff1a94f4c265a8def)