OpenStack Swift Proxy Charm

NRPE healthcheck picks incorrect port with https

Bug #1702847 reported by Peter Sabaini
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Swift Proxy Charm
Fix Released
Undecided
Peter Sabaini
OpenStack Swift Proxy Charm 17.08

Bug Description

The NRPE healthcheck is hardcoded included with swift-proxy uses a fixed api port, 8070, to talk to swift. However, the charm configures the api port differently if swift-proxy is configured for https.

Revision history for this message
Peter Sabaini (peter-sabaini) wrote :

https://review.openstack.org/#/c/481522/

Changed in charm-swift-proxy:
assignee: nobody → Peter Sabaini (peter-sabaini)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-swift-proxy (master)

Reviewed: https://review.openstack.org/481522
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=4fb8fb803960e51f41899667e56315b41f66ec9e
Submitter: Jenkins
Branch: master

commit 4fb8fb803960e51f41899667e56315b41f66ec9e
Author: Peter Sabaini <email address hidden>
Date: Fri Jul 7 10:38:03 2017 +0200

    Don't hardcode api port, use helper to determine port

    The NRPE healthcheck included with swift-proxy uses hardcoded api
    port, 8070, to talk to swift. However, the charm configures the api
    port differently if swift-proxy is configured for https.

    Closes-Bug: 1702847
    Change-Id: I3e8d025e66799d9eb24ede530b6a7d0936613620

Changed in charm-swift-proxy:
status: In Progress → Fix Committed
James Page (james-page)
Changed in charm-swift-proxy:
milestone: none → 17.08
James Page (james-page)
Changed in charm-swift-proxy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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