[Yahoo-eng-team] [Bug 1263032] [NEW] Timeout while waiting on RPC response - topic: "compute.devstack-*", RPC method: "get_console_output" info: ""
Public bug reported: http://logs.openstack.org/82/25882/10/check/check-tempest-dsvm- full/01bb021/logs/screen-n-api.txt.gz?level=TRACE#_2013-12-20_06_40_39_590 2013-12-20 06:40:39.590 ERROR nova.api.openstack Caught error: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" <...> 2013-12-20 06:40:39.590 25870 TRACE nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" Because of this, the gate job of check-tempest-dsvm-full has been failed. logstash query: message:"nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: \"" AND message:", RPC method: \"get_console_output\"" ** Affects: nova Importance: Undecided Status: New ** Description changed: http://logs.openstack.org/82/25882/10/check/check-tempest-dsvm- full/01bb021/logs/screen-n-api.txt.gz?level=TRACE#_2013-12-20_06_40_39_590 2013-12-20 06:40:39.590 ERROR nova.api.openstack Caught error: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" <...> 2013-12-20 06:40:39.590 25870 TRACE nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" Because of this, the gate job of check-tempest-dsvm-full has been failed. logstash query: message:"nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: \"" AND message:", RPC method: - \"get_console_output\" + \"get_console_output\"" -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1263032 Title: Timeout while waiting on RPC response - topic: "compute.devstack-*", RPC method: "get_console_output" info: "" Status in OpenStack Compute (Nova): New Bug description: http://logs.openstack.org/82/25882/10/check/check-tempest-dsvm- full/01bb021/logs/screen-n-api.txt.gz?level=TRACE#_2013-12-20_06_40_39_590 2013-12-20 06:40:39.590 ERROR nova.api.openstack Caught error: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" <...> 2013-12-20 06:40:39.590 25870 TRACE nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: "compute.devstack-precise-hpcloud-az2-902809", RPC method: "get_console_output" info: "" Because of this, the gate job of check-tempest-dsvm-full has been failed. logstash query: message:"nova.api.openstack Timeout: Timeout while waiting on RPC response - topic: \"" AND message:", RPC method: \"get_console_output\"" To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1263032/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229324] Re: extraneous vim editor configuration comments
** Also affects: tempest 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/1229324 Title: extraneous vim editor configuration comments Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Committed Status in Orchestration API (Heat): In Progress Status in OpenStack Neutron (virtual network service): New Status in Oslo - a Library of Common OpenStack Code: Fix Committed Status in Python client library for Ceilometer: In Progress Status in Python client library for heat: Fix Committed Status in Python client library for Neutron: New Status in OpenStack Object Storage (Swift): New Status in Tempest: In Progress Bug description: Many of the source code files have a beginning line # vim: tabstop=4 shiftwidth=4 softtabstop=4 This should be deleted. Many of these lines are in the ceilometer/openstack/common directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1229324/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1271416] [NEW] tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON.setupClass(): TimeoutException: Request timed out
Public bug reported: ft7.1: setUpClass (tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)_StringException: Traceback (most recent call last): File "tempest/api/compute/images/test_list_image_filters.py", line 60, in setUpClass cls.server1['id'], wait_until='ACTIVE') File "tempest/api/compute/base.py", line 211, in create_image_from_server kwargs['wait_until']) File "tempest/services/compute/json/images_client.py", line 85, in wait_for_image_status waiters.wait_for_image_status(self, image_id, status) File "tempest/common/waiters.py", line 124, in wait_for_image_status raise exceptions.TimeoutException(message) TimeoutException: Request timed out Details: Image 41113dda-a32b-42d2-a326-6c135b58120a failed to reach ACTIVE status within the required time (196 s). Current status: SAVING. Sample failure: http://logs.openstack.org/09/68009/1/check/check- tempest-dsvm-postgres-full/676b390/ logstash query for the failure string: http://logstash.openstack.org/index.html#eyJzZWFyY2giOiJmaWxlbmFtZTpcImNvbnNvbGUuaHRtbFwiIEFORCBtZXNzYWdlOlwiZmFpbGVkIHRvIHJlYWNoIEFDVElWRSBzdGF0dXMgd2l0aGluIHRoZSByZXF1aXJlZCB0aW1lXCIgQU5EIG1lc3NhZ2U6XCJTQVZJTkcuXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTAzNjg0ODg2NjR9 ** Affects: nova Importance: Undecided Status: New ** Tags: image testing -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1271416 Title: tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON.setupClass(): TimeoutException: Request timed out Status in OpenStack Compute (Nova): New Bug description: ft7.1: setUpClass (tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)_StringException: Traceback (most recent call last): File "tempest/api/compute/images/test_list_image_filters.py", line 60, in setUpClass cls.server1['id'], wait_until='ACTIVE') File "tempest/api/compute/base.py", line 211, in create_image_from_server kwargs['wait_until']) File "tempest/services/compute/json/images_client.py", line 85, in wait_for_image_status waiters.wait_for_image_status(self, image_id, status) File "tempest/common/waiters.py", line 124, in wait_for_image_status raise exceptions.TimeoutException(message) TimeoutException: Request timed out Details: Image 41113dda-a32b-42d2-a326-6c135b58120a failed to reach ACTIVE status within the required time (196 s). Current status: SAVING. Sample failure: http://logs.openstack.org/09/68009/1/check/check- tempest-dsvm-postgres-full/676b390/ logstash query for the failure string: http://logstash.openstack.org/index.html#eyJzZWFyY2giOiJmaWxlbmFtZTpcImNvbnNvbGUuaHRtbFwiIEFORCBtZXNzYWdlOlwiZmFpbGVkIHRvIHJlYWNoIEFDVElWRSBzdGF0dXMgd2l0aGluIHRoZSByZXF1aXJlZCB0aW1lXCIgQU5EIG1lc3NhZ2U6XCJTQVZJTkcuXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTAzNjg0ODg2NjR9 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1271416/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1281936] [NEW] A v3 API request of "GET /versions/:(id)" occurs "Unexpected API Error."
Public bug reported:
When I request a v3 API request of "GET /versions/:(id)" occurs "Unexpected API
Error.".
$ curl -i 'http://192.168.1.36:8774/v3/versions/123' -X GET -H
"X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token: "
HTTP/1.1 500 Internal Server Error
Content-Length: 193
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-baf6f903-b3f1-4c80-9e59-93f1440609a4
Date: Wed, 19 Feb 2014 07:08:13 GMT
{"computeFault": {"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n", "code": 500}}
nova-api logged an error:
2014-02-19 16:14:37.075 ERROR nova.api.openstack.extensions
[req-282a97a5-8f42-4410-a8dd-ff97457d0241 admin demo] Unexpected exception in
API method
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions Traceback (most
recent call last):
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 472, in wrapped
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions return f(*args,
**kwargs)
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions TypeError: show()
got an unexpected keyword argument 'id'
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1281936
Title:
A v3 API request of "GET /versions/:(id)" occurs "Unexpected API
Error."
Status in OpenStack Compute (Nova):
New
Bug description:
When I request a v3 API request of "GET /versions/:(id)" occurs "Unexpected
API Error.".
$ curl -i 'http://192.168.1.36:8774/v3/versions/123' -X GET -H
"X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token: "
HTTP/1.1 500 Internal Server Error
Content-Length: 193
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-baf6f903-b3f1-4c80-9e59-93f1440609a4
Date: Wed, 19 Feb 2014 07:08:13 GMT
{"computeFault": {"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n", "code": 500}}
nova-api logged an error:
2014-02-19 16:14:37.075 ERROR nova.api.openstack.extensions
[req-282a97a5-8f42-4410-a8dd-ff97457d0241 admin demo] Unexpected exception in
API method
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions Traceback (most
recent call last):
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 472, in wrapped
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions return
f(*args, **kwargs)
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions TypeError: show()
got an unexpected keyword argument 'id'
2014-02-19 16:14:37.075 TRACE nova.api.openstack.extensions
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1281936/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1285598] [NEW] tempest failure: test_security_groups_basic_ops failes with MismatchError
Public bug reported: Jenkins job 'check-tempest-dsvm-neutron' failed. http://logs.openstack.org/24/74124/3/check/check-tempest-dsvm-neutron/b7488b4/logs/testr_results.html.gz Failed test is as follows: --- Traceback (most recent call last): File "tempest/scenario/test_security_groups_basic_ops.py", line 168, in setUp self._verify_mac_addr(self.primary_tenant) File "tempest/scenario/test_security_groups_basic_ops.py", line 456, in _verify_mac_addr self.assertIn((subnet_id, server_ip, mac_addr), port_detail_list) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 327, in assertIn self.assertThat(haystack, Contains(needle)) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in assertThat raise mismatch_error MismatchError: (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', None, 'fa:16:3e:a0:a9:f8') not in [(u'94bee2b4-b5a7-4465-8221-d97f8ba098a6', u'10.100.0.1', u'fa:16:3e:2e:ab:ca'), (u'94bee2b4-b5a7-4465-8221-d97f8ba098a6', u'10.100.0.2', u'fa:16:3e:e3:0c:03'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.3', u'fa:16:3e:4f:4b:c4'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.2', u'fa:16:3e:9d:87:dc'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.9', u'fa:16:3e:18:0d:5b'), (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', u'10.100.0.19', u'fa:16:3e:34:9a:af'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.1', u'fa:16:3e:5d:81:e2'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.8', u'fa:16:3e:8b:49:d4'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.34', u'fa:16:3e:62:c8:6e'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.3', u'fa:16:3e:2d:8c:34'), (u'8848e40b-515d-498a-9fd7-9173f333bf86', u'10.100.0.1', u'fa:16:3e:6b:50:a9'), (u'0ac4d00d-502f-4412-9107-826 504c5c032', u'172.24.4.36', u'fa:16:3e:9b:16:10'), (u'5d10320c-d47d-4b30-814b-69539dca4074', u'10.100.0.2', u'fa:16:3e:e9:df:6c'), (u'79363d87-0c23-4d70-9770-35270201946e', u'10.100.0.1', u'fa:16:3e:5e:45:0a'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.2', u'fa:16:3e:99:7d:3b'), (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', u'10.100.0.18', u'fa:16:3e:a0:a9:f8'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.35', u'fa:16:3e:6e:ac:cc'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.37', u'fa:16:3e:7a:46:04'), (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', u'10.100.0.17', u'fa:16:3e:0c:06:35'), (u'5d10320c-d47d-4b30-814b-69539dca4074', u'10.100.0.1', u'fa:16:3e:93:b3:de')] --- It seems this happens occasionally. http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiX3ZlcmlmeV9tYWNfYWRkclwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiIxNzI4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzkzNDk3NTEwNjYwfQ== ** 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/1285598 Title: tempest failure: test_security_groups_basic_ops failes with MismatchError Status in OpenStack Neutron (virtual network service): New Bug description: Jenkins job 'check-tempest-dsvm-neutron' failed. http://logs.openstack.org/24/74124/3/check/check-tempest-dsvm-neutron/b7488b4/logs/testr_results.html.gz Failed test is as follows: --- Traceback (most recent call last): File "tempest/scenario/test_security_groups_basic_ops.py", line 168, in setUp self._verify_mac_addr(self.primary_tenant) File "tempest/scenario/test_security_groups_basic_ops.py", line 456, in _verify_mac_addr self.assertIn((subnet_id, server_ip, mac_addr), port_detail_list) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 327, in assertIn self.assertThat(haystack, Contains(needle)) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in assertThat raise mismatch_error MismatchError: (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', None, 'fa:16:3e:a0:a9:f8') not in [(u'94bee2b4-b5a7-4465-8221-d97f8ba098a6', u'10.100.0.1', u'fa:16:3e:2e:ab:ca'), (u'94bee2b4-b5a7-4465-8221-d97f8ba098a6', u'10.100.0.2', u'fa:16:3e:e3:0c:03'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.3', u'fa:16:3e:4f:4b:c4'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.2', u'fa:16:3e:9d:87:dc'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.9', u'fa:16:3e:18:0d:5b'), (u'5fc23b6b-14e0-480f-b766-5b6dbc670aa6', u'10.100.0.19', u'fa:16:3e:34:9a:af'), (u'ffca826c-0bfe-46ef-9090-00f29e3bc6d6', u'10.1.0.1', u'fa:16:3e:5d:81:e2'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.8', u'fa:16:3e:8b:49:d4'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.34', u'fa:16:3e:62:c8:6e'), (u'0ac4d00d-502f-4412-9107-826504c5c032', u'172.24.4.3', u'fa:16:3e:2d:8c:34'), (u'8848e40b-515d-498a-9fd7-9173f333bf86', u'10.100.0.1', u'fa:16:3e:6b:50:a9'), (u'0ac4d00d-502f-44
[Yahoo-eng-team] [Bug 1288214] [NEW] Calling GET v3/os-cells/capacities causes an 'Unexpected API Error.'
Public bug reported:
When I called Nova V3 API 'GET v3/os-cells/capacities', an 'Unexpected
API Error.' occurred.
http://logs.openstack.org/57/78157/1/check/check-tempest-dsvm-full/bcb3b6b/console.html#_2014-03-05_11_56_34_285
console.html
--
2014-03-05 11:56:34.283 | pythonlogging:'': {{{
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request: POST
http://127.0.0.1:5000/v2.0/tokens
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,083 Request Body: {"auth":
{"tenantName": "CellsV3Test-1270506035", "passwordCredentials": {"username":
"CellsV3Test-365545871", "password": "pass"}}}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Status: 200
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Headers:
{'content-length': '10648', 'date': 'Wed, 05 Mar 2014 11:30:18 GMT',
'content-type': 'application/json', 'vary': 'X-Auth-Token', 'connection':
'close'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Body: {"access":
{"token": {"issued_at": "2014-03-05T11:30:18.255082", "expires":
"2014-03-05T12:30:18Z", "id": "
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Large body (10648) md5
summary: a72282e83c228bfcf861c768bbcbdf79
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request: GET
http://127.0.0.1:8774/v3/os-cells/capacities
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json',
'X-Auth-Token': ''}
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Status: 500
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Nova/Cinder request id:
req-ae22c360-c3b8-4ad5-86d1-37e5664fb9ea
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Headers:
{'content-length': '216', 'date': 'Wed, 05 Mar 2014 11:31:18 GMT',
'content-type': 'application/json; charset=UTF-8', 'connection': 'close'}
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Body:
{"computeFault": {"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if
possible.\n", "code": 500}}
2014-03-05 11:56:34.285 | }}}
--
Full logs are:
http://logs.openstack.org/57/78157/1/check/check-tempest-dsvm-full/bcb3b6b
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1288214
Title:
Calling GET v3/os-cells/capacities causes an 'Unexpected API Error.'
Status in OpenStack Compute (Nova):
New
Bug description:
When I called Nova V3 API 'GET v3/os-cells/capacities', an 'Unexpected
API Error.' occurred.
http://logs.openstack.org/57/78157/1/check/check-tempest-dsvm-full/bcb3b6b/console.html#_2014-03-05_11_56_34_285
console.html
--
2014-03-05 11:56:34.283 | pythonlogging:'': {{{
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request: POST
http://127.0.0.1:5000/v2.0/tokens
2014-03-05 11:56:34.283 | 2014-03-05 11:30:18,083 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,083 Request Body: {"auth":
{"tenantName": "CellsV3Test-1270506035", "passwordCredentials": {"username":
"CellsV3Test-365545871", "password": "pass"}}}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Status: 200
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Headers:
{'content-length': '10648', 'date': 'Wed, 05 Mar 2014 11:30:18 GMT',
'content-type': 'application/json', 'vary': 'X-Auth-Token', 'connection':
'close'}
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Response Body: {"access":
{"token": {"issued_at": "2014-03-05T11:30:18.255082", "expires":
"2014-03-05T12:30:18Z", "id": "
2014-03-05 11:56:34.284 | 2014-03-05 11:30:18,312 Large body (10648) md5
summary: a72282e83c228bfcf861c768bbcbdf79
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request: GET
http://127.0.0.1:8774/v3/os-cells/capacities
2014-03-05 11:56:34.285 | 2014-03-05 11:30:18,313 Request Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json',
'X-Auth-Token': ''}
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Status: 500
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Nova/Cinder request id:
req-ae22c360-c3b8-4ad5-86d1-37e5664fb9ea
2014-03-05 11:56:34.285 | 2014-03-05 11:31:18,373 Response Headers:
{'content-length': '216'
[Yahoo-eng-team] [Bug 1306390] Re: os-fping API is not available by default in Ubuntu
Fix proposed to branch: master Review: https://review.openstack.org/#/c/87504/ ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Masayuki Igawa (igawa) ** Changed in: devstack Status: In Progress => Invalid ** Changed in: nova Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1306390 Title: os-fping API is not available by default in Ubuntu Status in devstack - openstack dev environments: Invalid Status in OpenStack Compute (Nova): In Progress Bug description: fping utility was introduced by https://bugs.launchpad.net/devstack/+bug/1287468 and https://review.openstack.org/77749. But we can't use it yet in Ubuntu. Because the Nova's default fping_path is '/usr/sbin/fping' but the path of Ubuntu is '/usr/bin/fping'. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1306390/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1779270] [NEW] live-migration tempest test failed because the instance didn't seem to migrate to its target host
Public bug reported:
Description
===
test_live_block_migration[0][1][2] tempest tests failed frequently[3].
[0]
http://status.openstack.org/openstack-health/#/test/tempest.api.compute.admin.test_live_migration.LiveMigrationTest.test_live_block_migration?duration=P1M
[1]
http://status.openstack.org/openstack-health/#/test/tempest.api.compute.admin.test_live_migration.LiveAutoBlockMigrationV225Test.test_live_block_migration?duration=P1M
[2]
http://status.openstack.org/openstack-health/#/test/tempest.api.compute.admin.test_live_migration.LiveMigrationRemoteConsolesV26Test.test_live_block_migration?duration=P1M
[3]
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Live%20Migration%20failed.%20Migrations%20list%20for%20Instance%20%5C%22
Steps to reproduce
==
* run nova-live-migration, neutron-tempest-multinode-full or some other job
which contains the test_live_block_migration test.
Expected result
===
* The test doesn't fail. The instance is migrated.
Actual result
=
* The instance doesn't seem to be migrated, and then, the test fails.
Environment
===
* In the gate, master branch. Not sure about the stable branches.
Logs & Configs
==
Quote from
http://logs.openstack.org/34/575734/8/gate/nova-live-migration/cb90e1d/job-output.txt.gz
2018-06-25 19:47:23.645249 | primary | 2018-06-25 19:47:23.643 | {1}
tempest.api.compute.admin.test_live_migration.LiveMigrationTest.test_live_block_migration
[25.911015s] ... FAILED
2018-06-25 19:47:23.647327 | primary | 2018-06-25 19:47:23.646 |
2018-06-25 19:47:23.653059 | primary | 2018-06-25 19:47:23.648 | Captured
traceback:
2018-06-25 19:47:23.655235 | primary | 2018-06-25 19:47:23.654 |
~~~
2018-06-25 19:47:23.657181 | primary | 2018-06-25 19:47:23.656 | Traceback
(most recent call last):
2018-06-25 19:47:23.658951 | primary | 2018-06-25 19:47:23.658 | File
"tempest/api/compute/admin/test_live_migration.py", line 127, in
test_live_block_migration
2018-06-25 19:47:23.664233 | primary | 2018-06-25 19:47:23.663 |
self._test_live_migration()
2018-06-25 19:47:23.669330 | primary | 2018-06-25 19:47:23.668 | File
"tempest/api/compute/admin/test_live_migration.py", line 117, in
_test_live_migration
2018-06-25 19:47:23.671351 | primary | 2018-06-25 19:47:23.670 |
self._live_migrate(server_id, destination_host, state, volume_backed)
2018-06-25 19:47:23.673324 | primary | 2018-06-25 19:47:23.672 | File
"tempest/api/compute/admin/test_live_migration.py", line 91, in _live_migrate
2018-06-25 19:47:23.676421 | primary | 2018-06-25 19:47:23.675 | msg)
2018-06-25 19:47:23.678566 | primary | 2018-06-25 19:47:23.678 | File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py",
line 411, in assertEqual
2018-06-25 19:47:23.680280 | primary | 2018-06-25 19:47:23.679 |
self.assertThat(observed, matcher, message)
2018-06-25 19:47:23.682290 | primary | 2018-06-25 19:47:23.681 | File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py",
line 498, in assertThat
2018-06-25 19:47:23.685235 | primary | 2018-06-25 19:47:23.683 | raise
mismatch_error
2018-06-25 19:47:23.688145 | primary | 2018-06-25 19:47:23.687 |
testtools.matchers._impl.MismatchError: !=:
2018-06-25 19:47:23.690041 | primary | 2018-06-25 19:47:23.689 | reference
= u'ubuntu-xenial-ovh-gra1-332527'
2018-06-25 19:47:23.691611 | primary | 2018-06-25 19:47:23.691 | actual
= u'ubuntu-xenial-ovh-gra1-332530'
2018-06-25 19:47:23.693251 | primary | 2018-06-25 19:47:23.692 | : Live
Migration failed. Migrations list for Instance
607cb757-f381-44b4-aff9-5cafe6d2cdfe: [
2018-06-25 19:47:23.695192 | primary | 2018-06-25 19:47:23.694 | {u'id': 9,
u'instance_uuid': u'607cb757-f381-44b4-aff9-5cafe6d2cdfe', u'status': u'error',
u'updated_at': u'2018-06-25T19:47:23.00', u'new_instance_type_id': 11,
u'old_instance_type_id': 11, u'source_node':
u'ubuntu-xenial-ovh-gra1-332530', u'dest_host': None, u'source_compute':
u'ubuntu-xenial-ovh-gra1-332530', u'dest_node':
u'ubuntu-xenial-ovh-gra1-332527', u'created_at':
u'2018-06-25T19:47:11.00', u'dest_compute':
u'ubuntu-xenial-ovh-gra1-332527'}]
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1779270
Title:
live-migration tempest test failed because the instance didn't seem to
migrate to its target host
Status in OpenStack Compute (nova):
New
Bug description:
Description
===
test_live_block_migration[0][1][2] tempest tests failed frequently[3].
[0]
http://status.openstack.org/openstack-health/#/test/tempest.api
[Yahoo-eng-team] [Bug 1512207] Re: Fix usage of assertions
As Jordan pointed out, assertTrue(...) is not the same as assertEqual(True,...). So we should do this very carefully if we need to do. But I don't think it's worth while to take the risk. ** Changed in: openstack-health Status: In Progress => Invalid ** Changed in: openstack-health Assignee: Swapnil Kulkarni (coolsvap) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1512207 Title: Fix usage of assertions Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Blazar: In Progress Status in Cinder: Invalid Status in congress: Fix Released Status in Cue: Fix Released Status in Glance: Won't Fix Status in Group Based Policy: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in kuryr: Fix Released Status in Magnum: In Progress Status in Manila: Fix Released Status in Murano: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Invalid Status in OpenStack Health: Invalid Status in os-brick: Fix Released Status in os-net-config: Fix Released Status in os-testr: In Progress Status in oslo.cache: Fix Released Status in oslo.messaging: Fix Released Status in Packstack: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Released Status in Rally: Fix Released Status in requests-mock: Won't Fix Status in Sahara: Fix Released Status in shaker: Fix Released Status in Solum: Fix Released Status in Stackalytics: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: Fix Released Status in watcher: Fix Released Status in zaqar: Fix Released Bug description: Manila should use the specific assertion: self.assertIsTrue/False(observed) instead of the generic assertion: self.assertEqual(True/False, observed) To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1512207/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
