← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1611750] [NEW] LBaaSv2 SELECT FOR UPDATE error in postgresql

 

Public bug reported:

When deleting or updating a lbaasv2 (creating a listener) in postgresql,
this error happens:

2016-07-26 07:20:42.611 15316 ERROR neutron.api.v2.resource DBError: (psycopg2.NotSupportedError) FOR UPDATE cannot be applied to the nullable side of an outer join
2016-07-26 07:20:42.611 15316 ERROR neutron.api.v2.resource  [SQL: 'SELECT lbaas_loadbalancers.tenant_id AS lbaas_loadbalancers_tenant_id, lbaas_loadbalancers.id AS lbaas_loadbalancers_id, lbaas_loadbalancers.name AS lbaas_loadbalancers_name, lbaas_loadbalancers.description AS lbaas_loadbalancers_description, lbaas_loadbalancers.vip_subnet_id AS lbaas_loadbalancers_vip_subnet_id, lbaas_loadbalancers.vip_port_id AS lbaas_loadbalancers_vip_port_id, lbaas_loadbalancers.vip_address AS lbaas_loadbalancers_vip_address, lbaas_loadbalancers.provisioning_status AS lbaas_loadbalancers_provisioning_status, lbaas_loadbalancers.operating_status AS lbaas_loadbalancers_operating_status, lbaas_loadbalancers.admin_state_up AS lbaas_loadbalancers_admin_state_up, lbaas_loadbalancer_statistics_1.loadbalancer_id AS lbaas_loadbalancer_statistics_1_loadbalancer_id, lbaas_loadbalancer_statistics_1.bytes_in AS lbaas_loadbalancer_statistics_1_bytes_in, lbaas_loadbalancer_statistics_1.bytes_out AS lbaas_loadbalancer_statistics_1_bytes_out, lbaas_loadbalancer_statistics_1.active_connections AS lbaas_loadbalancer_statistics_1_active_connections, lbaas_loadbalancer_statistics_1.total_connections AS lbaas_loadbalancer_statistics_1_total_connections, providerresourceassociations_1.provider_name AS providerresourceassociations_1_provider_name, providerresourceassociations_1.resource_id AS providerresourceassociations_1_resource_id \nFROM lbaas_loadbalancers LEFT OUTER JOIN lbaas_loadbalancer_statistics AS lbaas_loadbalancer_statistics_1 ON lbaas_loadbalancers.id = lbaas_loadbalancer_statistics_1.loadbalancer_id LEFT OUTER JOIN providerresourceassociations AS providerresourceassociations_1 ON lbaas_loadbalancers.id = providerresourceassociations_1.resource_id \nWHERE lbaas_loadbalancers.id = %(id_1)s FOR UPDATE'] [parameters: {'id_1': u'7edbcecc-9621-4fb5-a8e8-a2d61037ca07'}]

The reason is explained in this thread:

https://www.postgresql.org/message-id/B15DF97D-188F-
4FD1-99B6-BCEB7E0C3E99%40socialserve.com

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  LBaaSv2 SELECT FOR UPDATE error in postgresql

Status in neutron:
  New

Bug description:
  When deleting or updating a lbaasv2 (creating a listener) in
  postgresql, this error happens:

  2016-07-26 07:20:42.611 15316 ERROR neutron.api.v2.resource DBError: (psycopg2.NotSupportedError) FOR UPDATE cannot be applied to the nullable side of an outer join
  2016-07-26 07:20:42.611 15316 ERROR neutron.api.v2.resource  [SQL: 'SELECT lbaas_loadbalancers.tenant_id AS lbaas_loadbalancers_tenant_id, lbaas_loadbalancers.id AS lbaas_loadbalancers_id, lbaas_loadbalancers.name AS lbaas_loadbalancers_name, lbaas_loadbalancers.description AS lbaas_loadbalancers_description, lbaas_loadbalancers.vip_subnet_id AS lbaas_loadbalancers_vip_subnet_id, lbaas_loadbalancers.vip_port_id AS lbaas_loadbalancers_vip_port_id, lbaas_loadbalancers.vip_address AS lbaas_loadbalancers_vip_address, lbaas_loadbalancers.provisioning_status AS lbaas_loadbalancers_provisioning_status, lbaas_loadbalancers.operating_status AS lbaas_loadbalancers_operating_status, lbaas_loadbalancers.admin_state_up AS lbaas_loadbalancers_admin_state_up, lbaas_loadbalancer_statistics_1.loadbalancer_id AS lbaas_loadbalancer_statistics_1_loadbalancer_id, lbaas_loadbalancer_statistics_1.bytes_in AS lbaas_loadbalancer_statistics_1_bytes_in, lbaas_loadbalancer_statistics_1.bytes_out AS lbaas_loadbalancer_statistics_1_bytes_out, lbaas_loadbalancer_statistics_1.active_connections AS lbaas_loadbalancer_statistics_1_active_connections, lbaas_loadbalancer_statistics_1.total_connections AS lbaas_loadbalancer_statistics_1_total_connections, providerresourceassociations_1.provider_name AS providerresourceassociations_1_provider_name, providerresourceassociations_1.resource_id AS providerresourceassociations_1_resource_id \nFROM lbaas_loadbalancers LEFT OUTER JOIN lbaas_loadbalancer_statistics AS lbaas_loadbalancer_statistics_1 ON lbaas_loadbalancers.id = lbaas_loadbalancer_statistics_1.loadbalancer_id LEFT OUTER JOIN providerresourceassociations AS providerresourceassociations_1 ON lbaas_loadbalancers.id = providerresourceassociations_1.resource_id \nWHERE lbaas_loadbalancers.id = %(id_1)s FOR UPDATE'] [parameters: {'id_1': u'7edbcecc-9621-4fb5-a8e8-a2d61037ca07'}]

  The reason is explained in this thread:

  https://www.postgresql.org/message-id/B15DF97D-188F-
  4FD1-99B6-BCEB7E0C3E99%40socialserve.com

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


Follow ups