← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1635449] [NEW] Too many pools created from heat template when both listeners and pools depend on a item

 

Public bug reported:

When you deploy a heat template that has both listeners and pools
depending on a item, due to the order of locking, you may get additional
pools created erroneously.

Excerpt of heat template showing the issue :

##### LOADBALANCERS #####

  test-loadbalancer:
    type: OS::Neutron::LBaaS::LoadBalancer
    properties:
      name: test
      description: test
      vip_subnet: { get_param: subnet }

##### LISTENERS #####

  http-listener:
    type: OS::Neutron::LBaaS::Listener
    depends_on: test-loadbalancer
    properties:
      name: listener1
      description: listener1
      protocol_port: 80
      loadbalancer: { get_resource: test-loadbalancer } 
      protocol: HTTP

  https-listener:
    type: OS::Neutron::LBaaS::Listener
    depends_on: http-listener
    properties:
      name: listener2
      description: listener2
      protocol_port: 443
      loadbalancer: { get_resource: test-loadbalancer }
      protocol: TERMINATED_HTTPS
      default_tls_container_ref: '<tls container>'

##### POOLS #####

  http-pool:
    type: OS::Neutron::LBaaS::Pool
    depends_on: http-listener
    properties:
      name: pool1
      description: pool1
      lb_algorithm: 'ROUND_ROBIN'
      listener: { get_resource: http-listener }
      protocol: HTTP

  https-pool:
    type: OS::Neutron::LBaaS::Pool
    depends_on: https-listener
    properties:
      name: pool2
      description: pool2
      lb_algorithm: 'ROUND_ROBIN'
      listener: { get_resource: https-listener }
      protocol: HTTP

After the http-listener is created, both a pool and another listener
attempt to create but we end up with a number of pools (not always the
same number).

** Affects: neutron
     Importance: Critical
         Status: Triaged


** Tags: lbaas mitaka-backport-potential newton-backport-potential

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

Title:
  Too many pools created from heat template when both listeners and
  pools depend on a item

Status in neutron:
  Triaged

Bug description:
  When you deploy a heat template that has both listeners and pools
  depending on a item, due to the order of locking, you may get
  additional pools created erroneously.

  Excerpt of heat template showing the issue :

  ##### LOADBALANCERS #####

    test-loadbalancer:
      type: OS::Neutron::LBaaS::LoadBalancer
      properties:
        name: test
        description: test
        vip_subnet: { get_param: subnet }

  ##### LISTENERS #####

    http-listener:
      type: OS::Neutron::LBaaS::Listener
      depends_on: test-loadbalancer
      properties:
        name: listener1
        description: listener1
        protocol_port: 80
        loadbalancer: { get_resource: test-loadbalancer } 
        protocol: HTTP

    https-listener:
      type: OS::Neutron::LBaaS::Listener
      depends_on: http-listener
      properties:
        name: listener2
        description: listener2
        protocol_port: 443
        loadbalancer: { get_resource: test-loadbalancer }
        protocol: TERMINATED_HTTPS
        default_tls_container_ref: '<tls container>'

  ##### POOLS #####

    http-pool:
      type: OS::Neutron::LBaaS::Pool
      depends_on: http-listener
      properties:
        name: pool1
        description: pool1
        lb_algorithm: 'ROUND_ROBIN'
        listener: { get_resource: http-listener }
        protocol: HTTP

    https-pool:
      type: OS::Neutron::LBaaS::Pool
      depends_on: https-listener
      properties:
        name: pool2
        description: pool2
        lb_algorithm: 'ROUND_ROBIN'
        listener: { get_resource: https-listener }
        protocol: HTTP

  After the http-listener is created, both a pool and another listener
  attempt to create but we end up with a number of pools (not always the
  same number).

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


Follow ups