octavia

Octavia v2 API members always come up in OFFLINE operating status

Bug #1678330 reported by Michael Johnson
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
octavia
Fix Released
High
Adam Harwell

Bug Description

In the Octavia v2 API members always come up in "OFFLINE" operating status. It should be "NO_MONITOR" if there is no health monitor assigned to the pool and "OFFLINE" if there is a health monitor.

octavia/db/prepare.py:159

Tags: lbaas-merge
OpenStack Infra (hudson-openstack)
Changed in octavia:
assignee: nobody → Adam Harwell (adam-harwell)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to octavia (master)

Reviewed: https://review.openstack.org/405932
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=8b2f89b87a78958013c994d459c459d49459752d
Submitter: Jenkins
Branch: master

commit 8b2f89b87a78958013c994d459c459d49459752d
Author: Sindhu Devale <email address hidden>
Date: Fri Dec 2 05:57:55 2016 +0000

    Introduce Octavia v2 API for Members

    This patch aligns Octavia v2 API for members with
    lbaasv2.

    GET all - /v2.0/lbaas/pools/<pool-id>/members
    GET one - /v2.0/lbaas/pools/<pool-id>/members/<member-id>
    POST - /v2.0/lbaas/pools/<pool-id>/members {<body>}
    PUT - /v2.0/lbaas/pools/<pool-id>/members/<member-id> {<body>}
    DELETE - /v2.0/lbaas/pools/<pool-id>/members/<member-id>

    Also fixes a few bugs from previous API commits and refactors
    some test code / adds missing tests.

    Note: This changes the default operating_status of Members from OFFLINE
    to NO_MONITOR in the *v1* API, if the pool has no Health Monitor.
    I see this as a bug fix.

    Co-Authored-By: Nakul Dahiwade <email address hidden>
    Co-Authored-By: Adam Harwell <email address hidden>

    Partially-Implements: #1616642
    Closes-Bug: #1678330
    Closes-Bug: #1678336
    Closes-Bug: #1678337
    Change-Id: I0e15ab70afd5bbbc8b94db0dc9e64f13146003e8

Changed in octavia:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/octavia 1.0.0.0b1

This issue was fixed in the openstack/octavia 1.0.0.0b1 development milestone.

Revision history for this message
Huseyin Cotuk (hcotuk) wrote :

Hello, I am using octavia 3.0.1 and still seeing the same issue. Any members created under a pool come up with offline operating status. Actually members respond to requests but they do not update their operating status in the DB. Any idea?

Revision history for this message
Huseyin Cotuk (hcotuk) wrote :

Sorry, my fault. There was a typo in octavia.conf under [health_manager]/controller_ip_port_list. So the amphora instance can not reach the controller and update the status. Please ignore the previous message.

Revision history for this message
Michael Johnson (johnsom) wrote :

Yes, this has long since been fixed. If you load balancer status is not updating, most likely your lb-mgmt-net is mis-configured and the health heartbeat packets are not making it back to the health manager processes.

Revision history for this message
issa alio (issa-alio) wrote :

Hello, I have the same issue s Huseyin Cotuk

I'm in Octavia 2.1 Version for Openstack Queens

all the members are in offline but the LB works.

how the synchronise the members status in DB.

thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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