swift api service checks use host net instead of configured storage-net

Bug #1401701 reported by Rev. Dr. Aaron M. Segura
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Christopher H. Laco

Bug Description

MaaS service API check is configured thusly:

# service_api_local_check.py swift_account_server --path /healtcheck 10.155.8.72 6002

10.155.8.72 is the host network. However, the account/container/object services are listening on storage-net, 172.29.244.x. in this case.

global_overrides:
  swift:
    part_power: 20
    weight: 100
    min_part_hours: 1
    repl_number: 3
    storage_network: 'br-storage'
    replication_network: 'br-storage'

cidr_networks:
  storage: 172.29.244.0/22

root@host:/usr/lib/rackspace-monitoring-agent/plugins# netstat -lpnt | grep 6002
tcp 0 0 172.29.244.74:6002 0.0.0.0:* LISTEN 44446/python

This causes all service api checks to fail. Checks should be using the network defined under swift: overrides.

*** ALSO, note that "/healthcheck" is misspelled in the command line of the health check. ***

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → High
Changed in openstack-ansible:
assignee: nobody → Christopher H. Laco (claco)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

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

Changed in openstack-ansible:
status: Confirmed → In Progress
tags: added: juno-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/141222
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=c2fb63bfdd7f5b9cf47a8598a5178543b794f8c0
Submitter: Jenkins
Branch: master

commit c2fb63bfdd7f5b9cf47a8598a5178543b794f8c0
Author: Christopher H. Laco <email address hidden>
Date: Thu Dec 11 18:37:12 2014 -0500

    Correct Swift service health checks

    The account, container, and object service checks currently fail
    because they are trying to connect to the {{ ansible_ssh_host }}
    address. The services are only bound to the storage network
    interface. This does not effect the proxy service as it is bound
    to all interfaces.

    Additionally, the health check url is misspelled for all services.

      - Use the storage network address for Swift service checks
      - Correct the health check url spelling

    Change-Id: I581ab1e58464e3a99edeb52039a7b8f6e88f3149
    Closes-Bug: #1401701

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (stable/juno)

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/141271

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (stable/juno)

Reviewed: https://review.openstack.org/141271
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=348dadac61a647a3469fd7bf3b1411df53f6457f
Submitter: Jenkins
Branch: stable/juno

commit 348dadac61a647a3469fd7bf3b1411df53f6457f
Author: Christopher H. Laco <email address hidden>
Date: Thu Dec 11 18:37:12 2014 -0500

    Correct Swift service health checks

    The account, container, and object service checks currently fail
    because they are trying to connect to the {{ ansible_ssh_host }}
    address. The services are only bound to the storage network
    interface. This does not effect the proxy service as it is bound
    to all interfaces.

    Additionally, the health check url is misspelled for all services.

      - Use the storage network address for Swift service checks
      - Correct the health check url spelling

    Change-Id: I581ab1e58464e3a99edeb52039a7b8f6e88f3149
    Closes-Bug: #1401701
    (cherry picked from commit c2fb63bfdd7f5b9cf47a8598a5178543b794f8c0)

tags: removed: juno-backport-potential
Changed in openstack-ansible:
milestone: none → 10.1.0
Changed in openstack-ansible:
milestone: 10.1.0 → 10.1.1
Changed in openstack-ansible:
milestone: 10.1.1 → 10.1.0
status: Fix Committed → Fix Released
Changed in openstack-ansible:
milestone: 10.1.0 → 10.1.1
no longer affects: openstack-ansible/juno
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.