Activity log for bug #1182754

Date Who What changed Old value New value Message
2013-05-22 06:12:48 Mauro S M Rodrigues bug added bug
2013-05-22 06:24:28 OpenStack Infra nova: status New In Progress
2013-06-03 16:19:28 Mauro S M Rodrigues description Currently we have 6 Tempest tests failing only when using postgresql: tempest.api.compute.admin.test_fixed_ips.FixedIPsTestJson.test_set_reserve_with_invalid_ip tempest.api.compute.admin.test_fixed_ips.FixedIPsTestXml.test_set_reserve_with_invalid_ip tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsTestJSON.test_delete_nonexistant_floating_ip tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsTestXML.test_delete_nonexistant_floating_ip tempest.api.compute.floating_ips.test_list_floating_ips.FloatingIPDetailsTestJSON.test_get_nonexistant_floating_ip_details tempest.api.compute.floating_ips.test_list_floating_ips.FloatingIPDetailsTestXML.test_get_nonexistant_floating_ip_details This happens cause the tests are request using a different data type again postgresql: in the fixed_ips tests it is not an ip and in the floating ips tests the ip id is bigger than postgresql's integer, causing sqlalchemy to raise DataError like: 2013-05-22 04:55:25.708 ERROR nova.api.openstack [req-5edb2331-ecfa-44c8-8935-039235e7f84f admin admin] Caught error: (DataError) invalid input syntax for type inet: "my.invalid.ip" LINE 3: ...ERE fixed_ips.deleted = 0 AND fixed_ips.address = 'my.invali... ^ 'SELECT fixed_ips.created_at AS fixed_ips_created_at, fixed_ips.updated_at AS fixed_ips_updated_at, fixed_ips.deleted_at AS fixed_ips_deleted_at, fixed_ips.deleted AS fixed_ips_deleted, fixed_ips.id AS fixed_ips_id, fixed_ips.address AS fixed_ips_address, fixed_ips.network_id AS fixed_ips_network_id, fixed_ips.virtual_interface_id AS fixed_ips_virtual_interface_id, fixed_ips.instance_uuid AS fixed_ips_instance_uuid, fixed_ips.allocated AS fixed_ips_allocated, fixed_ips.leased AS fixed_ips_leased, fixed_ips.reserved AS fixed_ips_reserved, fixed_ips.host AS fixed_ips_host \nFROM fixed_ips \nWHERE fixed_ips.deleted = %(deleted_1)s AND fixed_ips.address = %(address_1)s \n LIMIT %(param_1)s' {'param_1': 1, 'address_1': u'my.invalid.ip', 'deleted_1': 0} Although all of them are valid test cases Currently we have 6 Tempest tests failing only when using postgresql: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- tempest.api.compute.admin.test_fixed_ips.FixedIPsTestJson.test_set_reserve_with_invalid_ip tempest.api.compute.admin.test_fixed_ips.FixedIPsTestXml.test_set_reserve_with_invalid_ip tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsTestJSON.test_delete_nonexistant_floating_ip tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsTestXML.test_delete_nonexistant_floating_ip tempest.api.compute.floating_ips.test_list_floating_ips.FloatingIPDetailsTestJSON.test_get_nonexistant_floating_ip_details tempest.api.compute.floating_ips.test_list_floating_ips.FloatingIPDetailsTestXML.test_get_nonexistant_floating_ip_details --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This happens cause the tests are request using a different data type again postgresql: in the fixed_ips tests it is not an ip and in the floating ips tests the ip id is bigger than postgresql's integer, causing sqlalchemy to raise DataError like: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 2013-05-22 04:55:25.708 ERROR nova.api.openstack [req-5edb2331-ecfa-44c8-8935-039235e7f84f admin admin] Caught error: (DataError) invalid input syntax for type inet: "my.invalid.ip" LINE 3: ...ERE fixed_ips.deleted = 0 AND fixed_ips.address = 'my.invali... ^ 'SELECT fixed_ips.created_at AS fixed_ips_created_at, fixed_ips.updated_at AS fixed_ips_updated_at, fixed_ips.deleted_at AS fixed_ips_deleted_at, fixed_ips.deleted AS fixed_ips_deleted, fixed_ips.id AS fixed_ips_id, fixed_ips.address AS fixed_ips_address, fixed_ips.network_id AS fixed_ips_network_id, fixed_ips.virtual_interface_id AS fixed_ips_virtual_interface_id, fixed_ips.instance_uuid AS fixed_ips_instance_uuid, fixed_ips.allocated AS fixed_ips_allocated, fixed_ips.leased AS fixed_ips_leased, fixed_ips.reserved AS fixed_ips_reserved, fixed_ips.host AS fixed_ips_host \nFROM fixed_ips \nWHERE fixed_ips.deleted = %(deleted_1)s AND fixed_ips.address = %(address_1)s \n LIMIT %(param_1)s' {'param_1': 1, 'address_1': u'my.invalid.ip', 'deleted_1': 0} --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Although all of them are valid test cases.
2013-06-03 16:19:28 Mauro S M Rodrigues tags postgresql
2013-06-04 14:05:29 David Ripton nova: importance Undecided High
2013-06-04 18:44:04 OpenStack Infra nova: status In Progress Fix Committed
2013-07-17 12:14:08 Thierry Carrez nova: status Fix Committed Fix Released
2013-07-17 12:14:08 Thierry Carrez nova: milestone havana-2
2013-10-17 11:46:21 Thierry Carrez nova: milestone havana-2 2013.2