yahoo-eng-team team mailing list archive

[Elena Ezhova <eezhova@xxxxxxxxxxxx>]

Public bug reported:

Description
===========

After making the following steps:
1. Create a pool
2. Create members
3. Create a VIP

The attempt to create a health monitor and associate it with the created pool
leads to the situation when the health monitor is shown as active
but it is not being added to /opt/stack/data/neutron/lbaas/<pool_id>/conf:

# neutron lb-healthmonitor-show c6ddc6e3-4a91-4a81-a110-fc3a44f311a0
+----------------+------------------------------------
| Field          | Value                                                              
+----------------+------------------------------------
| admin_state_up | True                                          
| delay          | 3                                                  
| expected_codes | 200                                     
| http_method    | GET                                                                                   
| id             | c6ddc6e3-4a91-4a81-a110-fc3a44f311a0                                
| max_retries    | 3                                                                  
| pools          | {"status": "ACTIVE", "status_description": null, "pool_id": "50497a9f-1439-431b-ac50-dd4cca0216fa"} 
| tenant_id      | dcf66bfd01aa4b82b10d8fb263ef375d                                 
| timeout        | 3                                                                              
| type           | HTTP                                                                                          
| url_path       | /                                                                                          
+----------------+------------------------------------

# cat /opt/stack/data/neutron/lbaas/50497a9f-1439-431b-ac50-dd4cca0216fa/conf                                       
global
        daemon
        user nobody
        group nogroup
        log /dev/log local0
        log /dev/log local1 notice
        stats socket /opt/stack/data/neutron/lbaas/50497a9f-1439-431b-ac50-dd4cca0216fa/sock mode 0666 level user
defaults
        log global
        retries 3
        option redispatch
        timeout connect 5000
        timeout client 50000
        timeout server 50000
frontend 5842ed27-02b9-499b-8512-bcf071a81ab2
        option tcplog
        bind 10.0.0.4:80
        mode http
        default_backend 50497a9f-1439-431b-ac50-dd4cca0216fa
        option forwardfor
backend 50497a9f-1439-431b-ac50-dd4cca0216fa
        mode http
        balance roundrobin
        option forwardfor
        server 78bbb52b-06e9-4eb6-9af9-95ecdf41c83d 10.0.0.3:80 weight 1

** Affects: neutron
     Importance: High
     Assignee: Oleg Bondarev (obondarev)
         Status: Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1259965

Title:
  [LBaaS] Creation of a health monitor after creating a VIP doesn't work
  correctly

Status in OpenStack Neutron (virtual network service):
  Confirmed

Bug description:
  Description
  ===========

  After making the following steps:
  1. Create a pool
  2. Create members
  3. Create a VIP

  The attempt to create a health monitor and associate it with the created pool
  leads to the situation when the health monitor is shown as active
  but it is not being added to /opt/stack/data/neutron/lbaas/<pool_id>/conf:

  # neutron lb-healthmonitor-show c6ddc6e3-4a91-4a81-a110-fc3a44f311a0
  +----------------+------------------------------------
  | Field          | Value                                                              
  +----------------+------------------------------------
  | admin_state_up | True                                          
  | delay          | 3                                                  
  | expected_codes | 200                                     
  | http_method    | GET                                                                                   
  | id             | c6ddc6e3-4a91-4a81-a110-fc3a44f311a0                                
  | max_retries    | 3                                                                  
  | pools          | {"status": "ACTIVE", "status_description": null, "pool_id": "50497a9f-1439-431b-ac50-dd4cca0216fa"} 
  | tenant_id      | dcf66bfd01aa4b82b10d8fb263ef375d                                 
  | timeout        | 3                                                                              
  | type           | HTTP                                                                                          
  | url_path       | /                                                                                          
  +----------------+------------------------------------

  # cat /opt/stack/data/neutron/lbaas/50497a9f-1439-431b-ac50-dd4cca0216fa/conf                                       
  global
          daemon
          user nobody
          group nogroup
          log /dev/log local0
          log /dev/log local1 notice
          stats socket /opt/stack/data/neutron/lbaas/50497a9f-1439-431b-ac50-dd4cca0216fa/sock mode 0666 level user
  defaults
          log global
          retries 3
          option redispatch
          timeout connect 5000
          timeout client 50000
          timeout server 50000
  frontend 5842ed27-02b9-499b-8512-bcf071a81ab2
          option tcplog
          bind 10.0.0.4:80
          mode http
          default_backend 50497a9f-1439-431b-ac50-dd4cca0216fa
          option forwardfor
  backend 50497a9f-1439-431b-ac50-dd4cca0216fa
          mode http
          balance roundrobin
          option forwardfor
          server 78bbb52b-06e9-4eb6-9af9-95ecdf41c83d 10.0.0.3:80 weight 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1259965/+subscriptions