[Yahoo-eng-team] [Bug 2049211] Re: neutron_tempest_plugin.api sorted() Function Issue
this is an issue on neutron-tempest-plugin's side, not tempest, i'll
change the component to neutron.
** Project changed: tempest => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2049211
Title:
neutron_tempest_plugin.api sorted() Function Issue
Status in neutron:
In Progress
Bug description:
Hi,
We got mismatch error in some tests as below. I debugged it and the
test passes if we change sorted() function. Because sorted() function
sorts by ascii character. When sorted in ASCII order, digits are
followed by uppercase characters and then lowercase characters. If I
have a network name starting with a capital letter, it gives an error.
If we change the sorted() function as follows, the test passed.
expected = sorted(retrieved_names, key=lambda x: (x.isdigit(), x.upper(),
x.lower()))
Example tests:
neutron_tempest_plugin.api.test_networks.NetworksSearchCriteriaTest.test_list_sorts_asc
neutron_tempest_plugin.api.test_networks.NetworksSearchCriteriaTest.test_list_sorts_desc
neutron_tempest_plugin.api.test_subnets.SubnetsSearchCriteriaTest.test_list_sorts_asc
neutron_tempest_plugin.api.test_subnets.SubnetsSearchCriteriaTest.test_list_sorts_desc
neutron_tempest_plugin.api.test_security_groups.SecGroupSearchCriteriaTest.test_list_sorts_by_name_asc
neutron_tempest_plugin.api.test_security_groups.SecGroupSearchCriteriaTest.test_list_sorts_by_name_desc
File: /etc/tempest/neutron-tempest-plugin/neutron_tempest_plugin/api/base.py
```
...
def _test_list_sorts(self, direction):
sort_args = {
'sort_dir': direction,
'sort_key': self.field
}
body = self.list_method(**sort_args)
resources = self._extract_resources(body)
self.assertNotEmpty(
resources, "%s list returned is empty" % self.resource)
retrieved_names = [res[self.field] for res in resources]
expected = sorted(retrieved_names)
if direction == constants.SORT_DIRECTION_DESC:
expected = list(reversed(expected))
self.assertEqual(expected, retrieved_names)
...
```
Debug:
retrieved_names
['', '', '', '123test', 'abc1', 'admin-x-x-net-01',
'admin-x-x-net-01', 'x--net', 'HA network tenant
2b09e7b2e1244fd4be2dc4092e39d17b', 'lb--net', 'm-temp--net',
'mxxx-xxx-xxx-net', 'mxxx---net', 'port-search-test-net',
'subnet-search-test-net', 'subnet-search-test-net', 'subnet-search-test-net',
'tempest-bgp-net', 'tempest-internal-dns-test-network-1876397349',
'tempest-internal-dns-test-network-332103665',
'tempest-MetadataTest-2030842204', 'tempest-test-network--1146463009',
'tempest-test-network--1164657513', 'tempest-test-network--1229813769',
'tempest-test-network--1233298883', 'tempest-test-network--1331054017',
'tempest-test-network--1415812209', 'tempest-test-network--1420967741',
'tempest-test-network--1424837927', 'tempest-test-network--1522800460',
'tempest-test-network--1542595587', 'tempest-test-network--1602874451',
'tempest-test-network--1651416667', 'tempest-test-network--1756609168',
'tempest-test-network--2053127518', '
tempest-test-network--2065848286', 'tempest-test-network--2086276043',
'tempest-test-network--234088028', 'tempest-test-network--303087501',
'tempest-test-network--377750320', 'tempest-test-network--433648246',
'tempest-test-network--488800423', 'tempest-test-network--52430',
'tempest-test-network--586734631', 'tempest-test-network--602944876',
'tempest-test-network--653992987', 'tempest-test-network-884004988', 'test1',
'test1', 'test10', 'testproject-other-net']
(Pdb) print(sorted(retrieved_names))
print(sorted(retrieved_names))
['', '', '', '123test', 'HA network tenant 2b09e7b2e1244fd4be2dc4092e39d17b',
'abc1', 'admin-x-x-net-01', 'admin-vprotect-provider-net-01',
'devxxx-xxx-net', 'lxxx-xxx-net', 'mxxx--x-net', 'mxxx--x-net',
'mxxx-xxx--net', 'port-search-test-net', 'subnet-search-test-net',
'subnet-search-test-net', 'subnet-search-test-net',
'tempest-MetadataTest-2030842204', 'tempest-bgp-net',
'tempest-internal-dns-test-network-1876397349',
'tempest-internal-dns-test-network-332103665',
'tempest-test-network--1146463009', 'tempest-test-network--1164657513',
'tempest-test-network--1229813769', 'tempest-test-network--1233298883',
'tempest-test-network--1331054017', 'tempest-test-network--1415812209',
'tempest-test-network--1420967741', 'tempest-test-network--1424837927',
'tempest-test-network--1522800460', 'tempest-test-network--1542595587',
'tempest-test-network--1602874451', 'tempest-test-network--1651416667',
'tempest-test-network--1756609168', 'tempest-test-network--20531
27518', 'tempest-test-network--2065848286',
'tempest-test-network--2086276043', 'tempest-test-network--234088028',
[Yahoo-eng-team] [Bug 2017023] Re: Tempest: remove test duplication for Compute legacy networking API and Neutron API calls
This effort is tracked in: https://etherpad.opendev.org/p/neutron-tempest-test_duplications There is only one tempest patch that has been merged already: https://review.opendev.org/c/openstack/tempest/+/892677 The rest of the patches tracked in the etherpad belong to neutron-tempest-plugin. Therefore, I'm closing this for tempest. ** Changed in: tempest Status: New => Fix Released -- 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/2017023 Title: Tempest: remove test duplication for Compute legacy networking API and Neutron API calls Status in neutron: New Status in OpenStack Compute (nova): New Status in tempest: Fix Released Bug description: In Tempest there are many tests under tempest.api.compute which calls Nova legacy API to create security-groups FIPs and similar. These APIs are legacy in Nova, and the calls only proxied toward Neutron (see [1] as example). There are similar tests under tempest.api.network and under tempest.scenario. I suggest to remove these calls, check if we can remove any tests that are redundant or move them to scenario group and change them to use Neutron API. [1]: https://opendev.org/openstack/nova/src/branch/master/nova/network/security_group_api.py#L370-L401 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2017023/+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 2004641] Re: ImageLocationsTest.test_replace_location fails intermittently
This hasn't occurred again for some time now.
I'll close this, it seems it got fixed by the change in tempest -
https://review.opendev.org/c/openstack/tempest/+/872982
Feel free to reopen and retriage if felt otherwise.
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2004641
Title:
ImageLocationsTest.test_replace_location fails intermittently
Status in Glance:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in tempest:
Fix Released
Bug description:
Saw a new gate failure happening a couple of times :
https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-7d,to:now))&_a=(columns:!(filename),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',key:filename,negate:!f,params:(query:job-
output.txt),type:phrase),query:(match_phrase:(filename:job-
output.txt,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',interval:auto,query:(language:kuery,query:test_replace_location),sort:!())
Example of a failed run :
2023-02-02 22:20:18.197006 | controller | ==
2023-02-02 22:20:18.197030 | controller | Failed 1 tests - output below:
2023-02-02 22:20:18.197050 | controller | ==
2023-02-02 22:20:18.197071 | controller |
2023-02-02 22:20:18.197095 | controller |
tempest.api.image.v2.test_images.ImageLocationsTest.test_replace_location[id-bf6e0009-c039-4884-b498-db074caadb10]
2023-02-02 22:20:18.197115 | controller |
--
2023-02-02 22:20:18.197134 | controller |
2023-02-02 22:20:18.197152 | controller | Captured traceback:
2023-02-02 22:20:18.197171 | controller | ~~~
2023-02-02 22:20:18.197190 | controller | Traceback (most recent call
last):
2023-02-02 22:20:18.197212 | controller |
2023-02-02 22:20:18.197234 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 875, in
test_replace_location
2023-02-02 22:20:18.197254 | controller | image =
self._check_set_multiple_locations()
2023-02-02 22:20:18.197273 | controller |
2023-02-02 22:20:18.197292 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 847, in
_check_set_multiple_locations
2023-02-02 22:20:18.197311 | controller | image =
self._check_set_location()
2023-02-02 22:20:18.197329 | controller |
2023-02-02 22:20:18.197351 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 820, in
_check_set_location
2023-02-02 22:20:18.197372 | controller |
self.client.update_image(image['id'], [
2023-02-02 22:20:18.197391 | controller |
2023-02-02 22:20:18.197410 | controller | File
"/opt/stack/tempest/tempest/lib/services/image/v2/images_client.py", line 40,
in update_image
2023-02-02 22:20:18.197429 | controller | resp, body =
self.patch('images/%s' % image_id, data, headers)
2023-02-02 22:20:18.197447 | controller |
2023-02-02 22:20:18.197465 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 346, in patch
2023-02-02 22:20:18.197490 | controller | return self.request('PATCH',
url, extra_headers, headers, body)
2023-02-02 22:20:18.197513 | controller |
2023-02-02 22:20:18.197533 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 720, in request
2023-02-02 22:20:18.197552 | controller | self._error_checker(resp,
resp_body)
2023-02-02 22:20:18.197571 | controller |
2023-02-02 22:20:18.197590 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 831, in
_error_checker
2023-02-02 22:20:18.197612 | controller | raise
exceptions.BadRequest(resp_body, resp=resp)
2023-02-02 22:20:18.197633 | controller |
2023-02-02 22:20:18.197655 | controller |
tempest.lib.exceptions.BadRequest: Bad request
2023-02-02 22:20:18.197674 | controller | Details: b'400 Bad Request\n\nThe
Store URI was malformed.\n\n '
2023-02-02 22:20:18.197692 | controller |
2023-02-02 22:20:18.197711 | controller |
2023-02-02 22:20:18.197729 | controller | Captured pythonlogging:
2023-02-02 22:20:18.197748 | controller | ~~~
2023-02-02 22:20:18.197774 | controller | 2023-02-02 22:01:06,773 114933
INFO [tempest.lib.common.rest_client] Request
(ImageLocationsTest:test_replace_location): 201 POST
https://10.210.193.38/image/v2/images 1.036s
2023-02-02 22:20:18.197798 | controller | 2023-02-02 22:01:06,774 114933
DEBUG[tempest.lib.common.rest_client] Request - Headers: {'Content-Type':
[Yahoo-eng-team] [Bug 2004641] Re: ImageLocationsTest.test_replace_location fails intermittently
This seems to be duplicate of https://bugs.launchpad.net/glance/+bug/1999800
I'll close this, it seems it got fixed by the change in tempest -
https://review.opendev.org/c/openstack/tempest/+/872982
Feel free to reopen and retriage if felt otherwise.
** Changed in: glance
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2004641
Title:
ImageLocationsTest.test_replace_location fails intermittently
Status in Glance:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in tempest:
Fix Released
Bug description:
Saw a new gate failure happening a couple of times :
https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-7d,to:now))&_a=(columns:!(filename),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',key:filename,negate:!f,params:(query:job-
output.txt),type:phrase),query:(match_phrase:(filename:job-
output.txt,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',interval:auto,query:(language:kuery,query:test_replace_location),sort:!())
Example of a failed run :
2023-02-02 22:20:18.197006 | controller | ==
2023-02-02 22:20:18.197030 | controller | Failed 1 tests - output below:
2023-02-02 22:20:18.197050 | controller | ==
2023-02-02 22:20:18.197071 | controller |
2023-02-02 22:20:18.197095 | controller |
tempest.api.image.v2.test_images.ImageLocationsTest.test_replace_location[id-bf6e0009-c039-4884-b498-db074caadb10]
2023-02-02 22:20:18.197115 | controller |
--
2023-02-02 22:20:18.197134 | controller |
2023-02-02 22:20:18.197152 | controller | Captured traceback:
2023-02-02 22:20:18.197171 | controller | ~~~
2023-02-02 22:20:18.197190 | controller | Traceback (most recent call
last):
2023-02-02 22:20:18.197212 | controller |
2023-02-02 22:20:18.197234 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 875, in
test_replace_location
2023-02-02 22:20:18.197254 | controller | image =
self._check_set_multiple_locations()
2023-02-02 22:20:18.197273 | controller |
2023-02-02 22:20:18.197292 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 847, in
_check_set_multiple_locations
2023-02-02 22:20:18.197311 | controller | image =
self._check_set_location()
2023-02-02 22:20:18.197329 | controller |
2023-02-02 22:20:18.197351 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 820, in
_check_set_location
2023-02-02 22:20:18.197372 | controller |
self.client.update_image(image['id'], [
2023-02-02 22:20:18.197391 | controller |
2023-02-02 22:20:18.197410 | controller | File
"/opt/stack/tempest/tempest/lib/services/image/v2/images_client.py", line 40,
in update_image
2023-02-02 22:20:18.197429 | controller | resp, body =
self.patch('images/%s' % image_id, data, headers)
2023-02-02 22:20:18.197447 | controller |
2023-02-02 22:20:18.197465 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 346, in patch
2023-02-02 22:20:18.197490 | controller | return self.request('PATCH',
url, extra_headers, headers, body)
2023-02-02 22:20:18.197513 | controller |
2023-02-02 22:20:18.197533 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 720, in request
2023-02-02 22:20:18.197552 | controller | self._error_checker(resp,
resp_body)
2023-02-02 22:20:18.197571 | controller |
2023-02-02 22:20:18.197590 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 831, in
_error_checker
2023-02-02 22:20:18.197612 | controller | raise
exceptions.BadRequest(resp_body, resp=resp)
2023-02-02 22:20:18.197633 | controller |
2023-02-02 22:20:18.197655 | controller |
tempest.lib.exceptions.BadRequest: Bad request
2023-02-02 22:20:18.197674 | controller | Details: b'400 Bad Request\n\nThe
Store URI was malformed.\n\n '
2023-02-02 22:20:18.197692 | controller |
2023-02-02 22:20:18.197711 | controller |
2023-02-02 22:20:18.197729 | controller | Captured pythonlogging:
2023-02-02 22:20:18.197748 | controller | ~~~
2023-02-02 22:20:18.197774 | controller | 2023-02-02 22:01:06,773 114933
INFO [tempest.lib.common.rest_client] Request
(ImageLocationsTest:test_replace_location): 201 POST
https://10.210.193.38/image/v2/images 1.036s
2023-02-02 22:20:18.197798 | controller | 2023-02-02 22:01:06,774 114933
DEBUG[tempest.lib.common.rest_client] Request -
[Yahoo-eng-team] [Bug 2004641] Re: ImageLocationsTest.test_replace_location fails intermittently
I didn't see that the job would fail because of the mentioned test the
whole month (July). I consider this fixed by
https://review.opendev.org/c/openstack/tempest/+/872982
** Changed in: tempest
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2004641
Title:
ImageLocationsTest.test_replace_location fails intermittently
Status in Glance:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in tempest:
Fix Released
Bug description:
Saw a new gate failure happening a couple of times :
https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-7d,to:now))&_a=(columns:!(filename),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',key:filename,negate:!f,params:(query:job-
output.txt),type:phrase),query:(match_phrase:(filename:job-
output.txt,index:'94869730-aea8-11ec-9e6a-83741af3fdcd',interval:auto,query:(language:kuery,query:test_replace_location),sort:!())
Example of a failed run :
2023-02-02 22:20:18.197006 | controller | ==
2023-02-02 22:20:18.197030 | controller | Failed 1 tests - output below:
2023-02-02 22:20:18.197050 | controller | ==
2023-02-02 22:20:18.197071 | controller |
2023-02-02 22:20:18.197095 | controller |
tempest.api.image.v2.test_images.ImageLocationsTest.test_replace_location[id-bf6e0009-c039-4884-b498-db074caadb10]
2023-02-02 22:20:18.197115 | controller |
--
2023-02-02 22:20:18.197134 | controller |
2023-02-02 22:20:18.197152 | controller | Captured traceback:
2023-02-02 22:20:18.197171 | controller | ~~~
2023-02-02 22:20:18.197190 | controller | Traceback (most recent call
last):
2023-02-02 22:20:18.197212 | controller |
2023-02-02 22:20:18.197234 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 875, in
test_replace_location
2023-02-02 22:20:18.197254 | controller | image =
self._check_set_multiple_locations()
2023-02-02 22:20:18.197273 | controller |
2023-02-02 22:20:18.197292 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 847, in
_check_set_multiple_locations
2023-02-02 22:20:18.197311 | controller | image =
self._check_set_location()
2023-02-02 22:20:18.197329 | controller |
2023-02-02 22:20:18.197351 | controller | File
"/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 820, in
_check_set_location
2023-02-02 22:20:18.197372 | controller |
self.client.update_image(image['id'], [
2023-02-02 22:20:18.197391 | controller |
2023-02-02 22:20:18.197410 | controller | File
"/opt/stack/tempest/tempest/lib/services/image/v2/images_client.py", line 40,
in update_image
2023-02-02 22:20:18.197429 | controller | resp, body =
self.patch('images/%s' % image_id, data, headers)
2023-02-02 22:20:18.197447 | controller |
2023-02-02 22:20:18.197465 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 346, in patch
2023-02-02 22:20:18.197490 | controller | return self.request('PATCH',
url, extra_headers, headers, body)
2023-02-02 22:20:18.197513 | controller |
2023-02-02 22:20:18.197533 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 720, in request
2023-02-02 22:20:18.197552 | controller | self._error_checker(resp,
resp_body)
2023-02-02 22:20:18.197571 | controller |
2023-02-02 22:20:18.197590 | controller | File
"/opt/stack/tempest/tempest/lib/common/rest_client.py", line 831, in
_error_checker
2023-02-02 22:20:18.197612 | controller | raise
exceptions.BadRequest(resp_body, resp=resp)
2023-02-02 22:20:18.197633 | controller |
2023-02-02 22:20:18.197655 | controller |
tempest.lib.exceptions.BadRequest: Bad request
2023-02-02 22:20:18.197674 | controller | Details: b'400 Bad Request\n\nThe
Store URI was malformed.\n\n '
2023-02-02 22:20:18.197692 | controller |
2023-02-02 22:20:18.197711 | controller |
2023-02-02 22:20:18.197729 | controller | Captured pythonlogging:
2023-02-02 22:20:18.197748 | controller | ~~~
2023-02-02 22:20:18.197774 | controller | 2023-02-02 22:01:06,773 114933
INFO [tempest.lib.common.rest_client] Request
(ImageLocationsTest:test_replace_location): 201 POST
https://10.210.193.38/image/v2/images 1.036s
2023-02-02 22:20:18.197798 | controller | 2023-02-02 22:01:06,774 114933
DEBUG[tempest.lib.common.rest_client] Request - Headers: {'Content-Type':
'application/json', 'Accept': 'application/json',
[Yahoo-eng-team] [Bug 2028123] Re: Jobs setting up more than 1 image fails with ValueError: invalid literal for int() with base 10: ''
Both patches are merged:
https://review.opendev.org/c/openstack/devstack/+/888906
https://review.opendev.org/c/openstack/devstack/+/888953
** Changed in: devstack
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2028123
Title:
Jobs setting up more than 1 image fails with ValueError: invalid
literal for int() with base 10: ''
Status in devstack:
Fix Released
Status in neutron:
New
Bug description:
Happening since the devstack patch
https://review.opendev.org/c/openstack/devstack/+/886795 merged.
Fails as below:-
2023-07-19 01:12:44.183383 | controller | +++
lib/tempest:configure_tempest:301: image_size_in_gib
2023-07-19 01:12:44.186369 | controller | +++
lib/tempest:image_size_in_gib:119: local size
2023-07-19 01:12:44.190924 | controller |
lib/tempest:image_size_in_gib:120: oscwrap --os-cloud devstack-admin
image show -c size -f value
2023-07-19 01:12:45.055357 | controller | usage: openstack image show [-h]
[-f {json,shell,table,value,yaml}]
2023-07-19 01:12:45.055438 | controller | [-c
COLUMN] [--noindent] [--prefix PREFIX]
2023-07-19 01:12:45.055450 | controller |
[--max-width ] [--fit-width]
2023-07-19 01:12:45.055460 | controller |
[--print-empty] [--human-readable]
2023-07-19 01:12:45.055469 | controller |
2023-07-19 01:12:45.055479 | controller | openstack image show: error: the
following arguments are required:
2023-07-19 01:12:45.170317 | controller | functions-common:oscwrap:2427
: return 2
2023-07-19 01:12:45.174387 | controller | +++
lib/tempest:image_size_in_gib:120: size=
2023-07-19 01:12:45.178301 | controller | +++
lib/tempest:image_size_in_gib:121: echo
2023-07-19 01:12:45.178524 | controller | +++
lib/tempest:image_size_in_gib:121: python3 -c 'import math;
print(int(math.ceil(float(int(input()) / 1024.0 ** 3'
2023-07-19 01:12:45.197214 | controller | Traceback (most recent call last):
2023-07-19 01:12:45.197249 | controller | File "", line 1, in
2023-07-19 01:12:45.197343 | controller | ValueError: invalid literal for
int() with base 10: ''
2023-07-19 01:12:45.205412 | controller | ++
lib/tempest:configure_tempest:301: disk=
2023-07-19 01:12:45.209824 | controller | + lib/tempest:configure_tempest:1
: exit_trap
2023-07-19 01:12:45.213259 | controller | + ./stack.sh:exit_trap:547
: local r=1
2023-07-19 01:12:45.218464 | controller | ++ ./stack.sh:exit_trap:548
: jobs -p
2023-07-19 01:12:45.224425 | controller | + ./stack.sh:exit_trap:548
: jobs=
2023-07-19 01:12:45.227487 | controller | + ./stack.sh:exit_trap:551
: [[ -n '' ]]
2023-07-19 01:12:45.232326 | controller | + ./stack.sh:exit_trap:557
: '[' -f /tmp/tmp.phuFS9io2I ']'
2023-07-19 01:12:45.236057 | controller | + ./stack.sh:exit_trap:558
: rm /tmp/tmp.phuFS9io2I
2023-07-19 01:12:45.241367 | controller | + ./stack.sh:exit_trap:562
: kill_spinner
2023-07-19 01:12:45.245280 | controller | + ./stack.sh:kill_spinner:457
: '[' '!' -z '' ']'
2023-07-19 01:12:45.249184 | controller | + ./stack.sh:exit_trap:564
: [[ 1 -ne 0 ]]
2023-07-19 01:12:45.254924 | controller | + ./stack.sh:exit_trap:565
: echo 'Error on exit'
2023-07-19 01:12:45.254945 | controller | Error on exit
2023-07-19 01:12:45.258724 | controller | + ./stack.sh:exit_trap:567
: type -p generate-subunit
2023-07-19 01:12:45.261436 | controller | + ./stack.sh:exit_trap:568
: generate-subunit 1689727847 1318 fail
2023-07-19 01:12:45.402879 | controller | + ./stack.sh:exit_trap:570
: [[ -z /opt/stack/logs ]]
2023-07-19 01:12:45.406897 | controller | + ./stack.sh:exit_trap:573
: /usr/bin/python3.10 /opt/stack/devstack/tools/worlddump.py -d
/opt/stack/logs
2023-07-19 01:12:45.440788 | controller | Traceback (most recent call last):
2023-07-19 01:12:45.440856 | controller | File
"/opt/stack/devstack/tools/worlddump.py", line 271, in
2023-07-19 01:12:45.440891 | controller | sys.exit(main())
2023-07-19 01:12:45.440911 | controller | File
"/opt/stack/devstack/tools/worlddump.py", line 248, in main
2023-07-19 01:12:45.440933 | controller | with io.open(fname, 'w') as f:
2023-07-19 01:12:45.440958 | controller | PermissionError: [Errno 13]
Permission denied: '/opt/stack/logs/worlddump-2023-07-19-011245.txt'
2023-07-19 01:12:45.447843 | controller | *** FINISHED ***
2023-07-19 01:12:46.151871 | controller | ERROR
Example
[Yahoo-eng-team] [Bug 2027817] Re: neutron slow jobs before xena broken with ERROR: unknown environment 'slow'
** Changed in: tempest Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2027817 Title: neutron slow jobs before xena broken with ERROR: unknown environment 'slow' Status in neutron: Invalid Status in tempest: Fix Released Bug description: Broken since https://review.opendev.org/c/openstack/tempest/+/887237 merged as neutron slow jobs inherit from tempest-slow-py3. These fails with ERROR: unknown environment 'slow' In releases before xena tempest is pinned and don't have the patch[1] which added slow toxenv. The job needs to be fixed such that these use available toxenv. Build failures:- https://zuul.opendev.org/t/openstack/builds?job_name=neutron-tempest- slow-py3=openstack/neutron Example failure:- https://1aa32956600eed195a6f-1e93f2912422e0b9805cacc7d195dee2.ssl.cf1.rackcdn.com/887279/1/gate/neutron- tempest-slow-py3/c9ff905/job-output.txt [1] https://github.com/openstack/tempest/commit/6bb98c2aa478f7ad32838fec4b59c4acb73ccf21 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2027817/+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 1959682] Re: String concatenation TypeError in resize flavor helper
*** This bug is a duplicate of bug 1959467 ***
https://bugs.launchpad.net/bugs/1959467
** This bug has been marked a duplicate of bug 1959467
QoSBandwidthAndPacketRateTests.test_server_resize_revert fails
intermittently with "{'code': 409, 'message': 'Flavor with name m1.nanoextra
already exists.'}"
--
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/1959682
Title:
String concatenation TypeError in resize flavor helper
Status in OpenStack Compute (nova):
Invalid
Status in tempest:
In Progress
Bug description:
In cae966812, for certain resize tests, we started adding a numeric ID
to the new flavor name to avoid collisions. This was incorrectly done
as a string + int concatenation, which is raising a `TypeError: can
only concatenate str (not "int") to str`.
Example of this happening in nova-next job:
https://zuul.opendev.org/t/openstack/build/7f750faf22ec48219ddd072cfe6e02e1/logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1959682/+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 1801919] Re: brctl is obsolete use ip
Marking this as fixed for devstack as "grep -r brctl" on master branch didn't return any results. ** Changed in: devstack Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1801919 Title: brctl is obsolete use ip Status in devstack: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Confirmed Status in os-vif: Fix Committed Bug description: bridge-utils (brctl) is obsolete, no modern software should depend on it. Used in: neutron/agent/linux/bridge_lib.py http://man7.org/linux/man-pages/man8/brctl.8.html Please use `ip` for basic bridge operations, than we can drop one obsolete dependency.. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1801919/+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 1927249] Re: Neutron_Tempest_Plugin: Create Fake Network for Negative Neutron Test cases
Moving to neutron as it's related to the neutron-tempest-plugin. ** Project changed: tempest => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1927249 Title: Neutron_Tempest_Plugin: Create Fake Network for Negative Neutron Test cases Status in neutron: New Bug description: There are some test cases which are modifying the test network UUID: https://github.com/openstack/neutron-tempest- plugin/blob/5ad4e821006b9ae2bbd5aee18f47b8764a2e2f9c/neutron_tempest_plugin/api/test_ports_negative.py#L56 Such updates are causing network leaks (Not deleted) The clean up deletes incorrect network ID and the actual network is left behind. Update the logic to deep-copy the Network Object/Restore the network ID after the test case is run To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927249/+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 1467589] Re: Remove Cinder V1 support
Done by https://review.opendev.org/c/openstack/grenade/+/481801/ ** Changed in: grenade Status: In Progress => Fix Released -- 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/1467589 Title: Remove Cinder V1 support Status in Cinder: Won't Fix Status in devstack: Fix Released Status in grenade: Fix Released Status in OpenStack Heat: Fix Released Status in OpenStack Compute (nova): Opinion Status in os-client-config: Fix Released Status in python-openstackclient: Fix Released Status in Rally: Fix Released Status in tempest: Fix Released Bug description: Cinder created v2 support in the Grizzly release. This is to track progress in removing v1 support in other projects. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1467589/+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 1917610] Re: Migration and resize tests from tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest failing in neutron-tempest-dvr-ha-multinode-full
https://review.opendev.org/c/openstack/tempest/+/778451 got merged
** Changed in: tempest
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1917610
Title:
Migration and resize tests from
tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest
failing in neutron-tempest-dvr-ha-multinode-full
Status in neutron:
New
Status in OpenStack Compute (nova):
Invalid
Status in tempest:
Fix Released
Bug description:
We saw it mostly in stable/train branch. Cold migration and resize
tests from
tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest
are failing due to errors like:
Traceback (most recent call last):
File "/opt/stack/tempest/tempest/common/utils/__init__.py", line 90, in
wrapper
return f(*func_args, **func_kwargs)
File
"/opt/stack/tempest/tempest/scenario/test_minbw_allocation_placement.py", line
262, in test_migrate_with_qos_min_bw_allocation
self.servers_client.migrate_server(server_id=server['id'])
File "/opt/stack/tempest/tempest/lib/services/compute/servers_client.py",
line 533, in migrate_server
return self.action(server_id, 'migrate', **kwargs)
File "/opt/stack/tempest/tempest/lib/services/compute/servers_client.py",
line 214, in action
post_body)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 300, in
post
return self.request('POST', url, extra_headers, headers, body, chunked)
File
"/opt/stack/tempest/tempest/lib/services/compute/base_compute_client.py", line
48, in request
method, url, extra_headers, headers, body, chunked)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 704, in
request
self._error_checker(resp, resp_body)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 815, in
_error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {'code': 400, 'message': 'No valid host was found. No valid host
found for cold migrate'}
See e.g.
https://0c345762207dc13e339e-d1e090fdf1a39e65d2b0ba37cbdce0a4.ssl.cf2.rackcdn.com/81/1/check/neutron-tempest-dvr-ha-multinode-full/463e963/testr_results.html
Logstash query which can be useful to find same issues:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22line%20262%2C%20in%20test_migrate_with_qos_min_bw_allocation%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1917610/+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 1914037] Re: scenario tests tempest.scenario.test_network_v6.TestGettingAddress fails
https://review.opendev.org/c/openstack/tempest/+/774764 got merged
** Changed in: tempest
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1914037
Title:
scenario tests tempest.scenario.test_network_v6.TestGettingAddress
fails
Status in neutron:
Invalid
Status in tempest:
Fix Released
Bug description:
scenario tests under group
tempest.scenario.test_network_v6.TestGettingAddress are failing
(observed on job tempest-slow on nova stable/rocky patches)
Example of failure:
https://7734cba1607fe472e545-7d211d4380eeb6317dc985091f0b7f02.ssl.cf5.rackcdn.com/761824/2/check/tempest-slow/e0359e0/testr_results.html
tempest.lib.exceptions.BadRequest: Bad request
Details: {u'message': u'Bad router request: Cidr 2001:db8::/64 of subnet
417e4c02-8b8a-4b89-bee2-32d35dc61b93 overlaps with cidr 2001:db8::/64 of subnet
56123648-b56d-486c-8919-a3e97802906f.', u'detail': u'', u'type': u'BadRequest'}
Could be because of recently merged patch
https://review.opendev.org/q/Id5d8ac09a38c656619f88a6f87b8f384fe4c55a8
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1914037/+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 1844568] Re: [compute] "create_test_server" if networks is undefined and more than one network is present
https://review.opendev.org/c/openstack/tempest/+/770169 got merged.
** Changed in: tempest
Status: In Progress => Fix Released
--
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/1844568
Title:
[compute] "create_test_server" if networks is undefined and more than
one network is present
Status in OpenStack Compute (nova):
Invalid
Status in tempest:
Fix Released
Bug description:
This problem was detected in "ServersNegativeTestJSON" [1]. When a
server is created ("cls.create_test_server"), if a network is not
defined but several networks are present in this project, Nova raises
the exception "NetworkAmbiguous", a seen in this log snippet:
Sep 13 23:44:15.520980 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: DEBUG nova.network.neutronv2.api [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] validate_networks() for None
{{(pid=27340) validate_networks
/opt/stack/nova/nova/network/neutronv2/api.py:2251}}
Sep 13 23:44:15.754945 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: INFO nova.api.openstack.wsgi [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] HTTP exception thrown: Multiple
possible networks found, use a Network ID to be more specific.
We can see that the network information provided to the server creation is
empty but Nova tries to assign a default single network for this server.
However Nova does not assign this default network because several networks are
present for this project ID. In this case, the server creation should be
specific passing the network information.
[1]https://58a87e825b9766115d07-cec36eea8e90c9127fc5a72b798cfeab.ssl.cf2.rackcdn.com/670177/9/check/networking-ovn-tempest-dsvm-ovs-release/b58638a/testr_results.html.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1844568/+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 1892837] Re: tempest.api.compute.servers.test_servers_negative fails in periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master
Fixed in tempest by
https://review.opendev.org/c/openstack/tempest/+/750661/ and released -
the change is part of 26.0.0 and 25.0.1 tags
** Changed in: tempest
Status: Fix Committed => Fix Released
--
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/1892837
Title:
tempest.api.compute.servers.test_servers_negative fails in periodic-
tripleo-ci-centos-8-standalone-full-tempest-api-master
Status in OpenStack Compute (nova):
Confirmed
Status in tempest:
Fix Released
Status in tripleo:
Fix Released
Bug description:
https://logserver.rdoproject.org/openstack-periodic-integration-
main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-
centos-8-standalone-full-tempest-api-
master/f9602c8/logs/undercloud/var/log/tempest/stestr_results.html.gz
ft1.1: setUpClass
(tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON)testtools.testresult.real._StringException:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/tempest/test.py", line 188, in
setUpClass
six.reraise(etype, value, trace)
File "/usr/local/lib/python3.6/site-packages/six.py", line 703, in reraise
raise value
File "/usr/lib/python3.6/site-packages/tempest/test.py", line 181, in
setUpClass
cls.resource_setup()
File
"/usr/lib/python3.6/site-packages/tempest/api/compute/servers/test_servers_negative.py",
line 64, in resource_setup
cls.client.delete_server(server['id'])
File
"/usr/lib/python3.6/site-packages/tempest/lib/services/compute/servers_client.py",
line 158, in delete_server
resp, body = self.delete("servers/%s" % server_id)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 329, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
"/usr/lib/python3.6/site-packages/tempest/lib/services/compute/base_compute_client.py",
line 48, in request
method, url, extra_headers, headers, body, chunked)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 702, in request
self._error_checker(resp, resp_body)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 879, in _error_checker
message=message)
tempest.lib.exceptions.ServerFault: Got server fault
Details: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
This is a real bug, we need someone from nova to take a look
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1892837/+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 1753209] Re: neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest, rbac policy in use across tenants.
Seems like this got fixed on neutron and neutron-tempest-plugin side ...
the LP is marked Fix Committed for tempest party, however there hasn't
been any commit merged/committed in tempest regarding this (or at least
i haven't found any), therefore I'm changing the state to Invalid .. If
my assumptions are not correct and the bug is still causing troubles,
please feel free to raise it and change the status of the LP
accordingly.
** Changed in: tempest
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1753209
Title:
neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest,
rbac policy in use across tenants.
Status in neutron:
Fix Released
Status in tempest:
Invalid
Status in tripleo:
Fix Released
Bug description:
neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest
failure
https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-
centos-7-ovb-1ctlr_1comp-featureset020-master/6cec620/tempest.html.gz
Details: {u'message': u'RBAC policy on object 3cfbd0a7-84f2-4e3f-917e-
bf51b5995e20 cannot be removed because other objects depend on
it.\nDetails: Callback
neutron.plugins.ml2.plugin.Ml2Plugin.validate_network_rbac_policy_change
--9223372036850840529 failed with "Unable to reconfigure sharing
settings for network 3cfbd0a7-84f2-4e3f-917e-bf51b5995e20. Multiple
tenants are using it.",Callback
neutron.services.network_ip_availability.plugin.NetworkIPAvailabilityPlugin.validate_network_rbac_policy_change
--9223372036853400817 failed with "Unable to reconfigure sharing
settings for network 3cfbd0a7-84f2-4e3f-917e-bf51b5995e20. Multiple
tenants are using it.",Callback
neutron.services.network_ip_availability.plugin.NetworkIPAvailabilityPlugin.validate_network_rbac_policy_change
--9223372036853463713 failed with "Unable to reconfigure sharing
settings for network 3cfbd0a7-84f2-4e3f-917e-bf51b5995e20. Multiple
tenants are using it."', u'type': u'RbacPolicyInUse', u'detail': u''}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1753209/+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 1906428] Re: test_cold_migrate_unshelved_instance failing with cat: can't open '/mnt/timestamp': No such file or directory
Based on the discussion above, it was agreed that the bug was on nova side (got fixed already) so marking this as Invalid for Tempest .. feel free to correct me ** Changed in: tempest Status: Confirmed => Invalid -- 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/1906428 Title: test_cold_migrate_unshelved_instance failing with cat: can't open '/mnt/timestamp': No such file or directory Status in OpenStack Compute (nova): Fix Released Status in tempest: Invalid Bug description: https://zuul.opendev.org/t/openstack/build/13400ea7d7af4dd88fca244b82301c79/log /job-output.txt#65297 2020-12-01 11:03:11.055150 | controller | 2020-12-01 10:52:58,178 102645 ERROR[tempest.lib.common.utils.linux.remote_client] (TestShelveInstance:test_cold_migrate_unshelved_instance) Executing command on 172.24.5.37 failed. Error: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; sudo cat /mnt/timestamp', exit status: 1, stderr: 2020-12-01 11:03:11.055160 | controller | cat: can't open '/mnt/timestamp': No such file or directory Add related test to Bug #1732428 https://review.opendev.org/c/openstack/tempest/+/743708 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1906428/+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 1906428] Re: test_cold_migrate_unshelved_instance failing with cat: can't open '/mnt/timestamp': No such file or directory
gerrit doesn't update status of the bugs automatically again ... this is supposed to be fixed for nova by https://review.opendev.org/c/openstack/nova/+/765561 ** Changed in: nova Status: In Progress => Fix Released -- 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/1906428 Title: test_cold_migrate_unshelved_instance failing with cat: can't open '/mnt/timestamp': No such file or directory Status in OpenStack Compute (nova): Fix Released Status in tempest: Invalid Bug description: https://zuul.opendev.org/t/openstack/build/13400ea7d7af4dd88fca244b82301c79/log /job-output.txt#65297 2020-12-01 11:03:11.055150 | controller | 2020-12-01 10:52:58,178 102645 ERROR[tempest.lib.common.utils.linux.remote_client] (TestShelveInstance:test_cold_migrate_unshelved_instance) Executing command on 172.24.5.37 failed. Error: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; sudo cat /mnt/timestamp', exit status: 1, stderr: 2020-12-01 11:03:11.055160 | controller | cat: can't open '/mnt/timestamp': No such file or directory Add related test to Bug #1732428 https://review.opendev.org/c/openstack/tempest/+/743708 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1906428/+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 1895876] Re: When accounts.yaml is used Tempest fails with "Invalid input for tenant_id. Reason: 'None' is not a valid string."
Changing the component to neutron as the mentioned failed tests belong
to neutron_tempest_plugin.
** Project changed: tempest => neutron
** Summary changed:
- When accounts.yaml is used Tempest fails with "Invalid input for tenant_id.
Reason: 'None' is not a valid string."
+ When accounts.yaml is used neutron_tempest_plugin fails with "Invalid input
for tenant_id. Reason: 'None' is not a valid string."
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1895876
Title:
When accounts.yaml is used neutron_tempest_plugin fails with "Invalid
input for tenant_id. Reason: 'None' is not a valid string."
Status in neutron:
New
Bug description:
When accounts.yaml is used Tempest fails with "Invalid input for
tenant_id. Reason: 'None' is not a valid string.". However the test
cases run fine when dynamic_credentials is set to true.
The test cases that fail are:
neutron_tempest_plugin.api.test_security_groups.SecGroupTest.test_list_security_group_rules_contains_all_rules
neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupQuotaTest.test_create_excess_sg
neutron_tempest_plugin.api.test_security_groups_negative.NegativeSecGroupRulesQuotaTest.test_sg_creation_with_insufficient_sg_rules_quota
In the last two test cases above, the tenant_id in the URL to update quota is
set to None.
200 PUT https://network-test.mydevstack.com/v2.0/quotas/None
Here's the trace...
1. When dynamic_credentials=false and accounts.yaml is used
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
"user": {"id": "f7cfb79d7e3949bca57cdc0a5726fcf6", "name":
"reddy-7026"}, "project": {"id": "6036590244c5a6e7e22299179bfa", "name":
"reddy-7026-DO-NOT-DELETE-tempest-proj"},
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
{"user": "id": "64b91e81a61a4ff9a53921225ef5c688", "name":
"reddy-7047"}, "project": {"id": "583b79fb166a49bda12ea53896e79ed6", "name":
"reddy-7047-DO-NOT-DELETE-tempest-proj"}
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
"user": {"id": "64b91e81a61a4ff9a53921225ef5c688", "name":
"reddy-7047"}, "project": {"id": "583b79fb166a49bda12ea53896e79ed6", "name":
"reddy-7047-DO-NOT-DELETE-tempest-proj"}
Request (NegativeSecGroupQuotaTest:test_create_excess_sg): 200 GET
https://network-test.mydevstack.com/v2.0/quotas/None
Body: b'{"quota": {"network": 100, "subnet": 100, "subnetpool": -1,
"port": 500, "router": 10, "floatingip": 50, "rbac_policy": 10,
"security_group": 10, "security_group_rule": 100, "trunk": -1}}
200 PUT https://network-test.mydevstack.com/v2.0/quotas/None
Body: {"quota": {"security_group": 0}}
Body: b'{"quota": {"network": 100, "subnet": 100, "subnetpool": -1,
"port": 500, "router": 10, "floatingip": 50, "rbac_policy": 10,
"security_group": 0, "security_group_rule": 100, "trunk": -1}}'
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
"user": {"id": "f7cfb79d7e3949bca57cdc0a5726fcf6", "name":
"reddy-7026"}, "project": {"id": "6036590244c5a6e7e22299179bfa", "name":
"reddy-7026-DO-NOT-DELETE-tempest-proj"}
201 POST https://network-test.mydevstack.com/v2.0/security-group
Body: {"security_group": {"name":
"tempest-NegativeSecGroupQuotaTest-709899598"}}
2. With dynamic_credentials=true
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
user": {"id": "c81d0a78edfd4c62a7baf28cc431ac71", "name": "admin"},
"project": {"id": "0d3df5dd5d794c41b7bde6d026f24fa2", "name": "admin"}
201 POST https://identity-test.mydevstack.com/v3/auth/tokens
"user": {"id": "c81d0a78edfd4c62a7baf28cc431ac71", "name": "admin"},
"project": {"id": "0d3df5dd5d794c41b7bde6d026f24fa2", "name": "admin"}
200 GET https://identity-test.mydevstack.com/v3/domains?name=Default
{"domains": [{"id": "default", "name": "Default", "description": "The
default domain", "enabled": true, "tags": [], "options": {}, "links": {"self":
"https://identity-test.mydevstack.com/v3/domains/default"}}], "links": {"next":
null, "self": "https://identity-test.mydevstack.com/v3/domains?name=Default;,
"previous": null}}
201 POST https://identity-test.mydevstack.com/v3/projects
{"project": {"description":
"tempest-NegativeSecGroupQuotaTest-1755512384-desc", "domain_id": "default",
"name": "tempest-NegativeSecGroupQuotaTest-1755512384"}}
{"project": {"id": "618161cd2c524aaba5ff107126941a89", "name":
"tempest-NegativeSecGroupQuotaTest-1755512384", "domain_id": "default",
"description": "tempest-NegativeSecGroupQuotaTest-1755512384-desc", "enabled":
true, "parent_id": "default", "is_domain": false, "tags": [], "options": {},
"links": {"self":
[Yahoo-eng-team] [Bug 1844568] Re: [compute] "create_test_server" if networks is undefined and more than one network is present
Seems like this is not fixed everywhere:
https://zuul.opendev.org/t/openstack/build/f1ae8eeb986a42e2b45d1a79e2e300e2
** Changed in: tempest
Status: Fix Released => 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/1844568
Title:
[compute] "create_test_server" if networks is undefined and more than
one network is present
Status in OpenStack Compute (nova):
Triaged
Status in tempest:
In Progress
Bug description:
This problem was detected in "ServersNegativeTestJSON" [1]. When a
server is created ("cls.create_test_server"), if a network is not
defined but several networks are present in this project, Nova raises
the exception "NetworkAmbiguous", a seen in this log snippet:
Sep 13 23:44:15.520980 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: DEBUG nova.network.neutronv2.api [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] validate_networks() for None
{{(pid=27340) validate_networks
/opt/stack/nova/nova/network/neutronv2/api.py:2251}}
Sep 13 23:44:15.754945 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: INFO nova.api.openstack.wsgi [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] HTTP exception thrown: Multiple
possible networks found, use a Network ID to be more specific.
We can see that the network information provided to the server creation is
empty but Nova tries to assign a default single network for this server.
However Nova does not assign this default network because several networks are
present for this project ID. In this case, the server creation should be
specific passing the network information.
[1]https://58a87e825b9766115d07-cec36eea8e90c9127fc5a72b798cfeab.ssl.cf2.rackcdn.com/670177/9/check/networking-ovn-tempest-dsvm-ovs-release/b58638a/testr_results.html.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1844568/+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 1844568] Re: [compute] "create_test_server" if networks is undefined and more than one network is present
After discussion with Ghanshyam we can consider this bug done.
kopecmartin gmann: thanks .. btw, is this still in progress? i see bunch of
merged reviews, isn't it done already?
https://bugs.launchpad.net/tempest/+bug/1844568 14:22
openstack Launchpad bug 1844568 in tempest "[compute]
"create_test_server" if networks is undefined and more than one network is
present" [Medium,In progress] - Assigned to Ghanshyam Mann (ghanshyammann)
14:22
gmann kopecmartin: we covered most of the tests and we kept this to find and
fix more tests but i have not seen network failure recently. 14:36
gmann kopecmartin: we can close this and if something comes up then just fix
it. 14:36
gmann without this bug link or just with ref to bug 14:36
kopecmartin ok, makes sense
** Changed in: tempest
Status: In Progress => Fix Released
--
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/1844568
Title:
[compute] "create_test_server" if networks is undefined and more than
one network is present
Status in OpenStack Compute (nova):
Triaged
Status in tempest:
Fix Released
Bug description:
This problem was detected in "ServersNegativeTestJSON" [1]. When a
server is created ("cls.create_test_server"), if a network is not
defined but several networks are present in this project, Nova raises
the exception "NetworkAmbiguous", a seen in this log snippet:
Sep 13 23:44:15.520980 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: DEBUG nova.network.neutronv2.api [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] validate_networks() for None
{{(pid=27340) validate_networks
/opt/stack/nova/nova/network/neutronv2/api.py:2251}}
Sep 13 23:44:15.754945 ubuntu-bionic-limestone-regionone-0011283625
devstack@n-api.service[27339]: INFO nova.api.openstack.wsgi [None
req-c95ecec2-8d10-4984-8ba9-b608161dd645
tempest-ServersNegativeTestJSON-445859222
tempest-ServersNegativeTestJSON-445859222] HTTP exception thrown: Multiple
possible networks found, use a Network ID to be more specific.
We can see that the network information provided to the server creation is
empty but Nova tries to assign a default single network for this server.
However Nova does not assign this default network because several networks are
present for this project ID. In this case, the server creation should be
specific passing the network information.
[1]https://58a87e825b9766115d07-cec36eea8e90c9127fc5a72b798cfeab.ssl.cf2.rackcdn.com/670177/9/check/networking-ovn-tempest-dsvm-ovs-release/b58638a/testr_results.html.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1844568/+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 1631872] Re: Not all neutron ports are ACTIVE after the vm spawns (hyper-v)
Seems like this got accidentally from Won't Fix state to InProgress without explanation why and any further work. Therefore I'm gonna move it back to Won't Fix. If you feel like this should be addressed , please provide the current info (as the bug is ~2 years old -> tempest code base has changed dramatically since then) and feel free to reopen. ** Changed in: tempest Status: In Progress => Won't Fix ** Changed in: tempest Assignee: Claudiu Belu (cbelu) => (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/1631872 Title: Not all neutron ports are ACTIVE after the vm spawns (hyper-v) Status in OpenStack Compute (nova): Fix Released Status in tempest: Won't Fix Bug description: Currently, the nova Hyper-V driver does not wait for neutron vif plug events (or, in case of other drivers, nova-compute can be configured not to wait for neutron vif plug events), which means that by the time the VM becomes ACTIVE, there's no guarantee that the ports have been bound and became ACTIVE. Because, of this, some tests which require connecting to the VM via a floating ip, will randomly fail [1], as tempest will filter out ports that are not active, raising an exception [2]. [1] http://paste.openstack.org/show/584712/ [2] https://github.com/openstack/tempest/blob/master/tempest/scenario/manager.py#L800 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1631872/+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 1881311] Re: Neutron Tempest Pagination test cases fail if run in parallel
I'm changing the project to neutron as it seems the problem is within
neutron tempest plugin, not tempest.
** Project changed: tempest => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1881311
Title:
Neutron Tempest Pagination test cases fail if run in parallel
Status in neutron:
New
Bug description:
Neutron tempest Pagination tet cases fail if run in parallel.
# Issue
The pagination test cases see items created by other test cases and hence
expected vs actual differ and the test cases fail.
# Proposed solution:
1. Update pagination test cases to query neutron resource only for a specific
project.
OR
2. Check the project ID in expected test data and use that Project ID to
match the results in Actual. Ignore any other Project ID
Open to further discussion or any other solution.
For Eg:
## These two test cases fail:
Test case 1:
neutron_tempest_plugin.api.test_trunk.TrunksSearchCriteriaTest.test_list_pagination_page_reverse_with_href_links[id-b4293e59-d794-4a93-be09-38667199ef68]
```code
Traceback
neutron_tempest_plugin.api.test_trunk.TrunksSearchCriteriaTest.test_list_pagination_page_reverse_with_href_links[id-b4293e59-d794-4a93-be09-38667199ef68]
Traceback: Traceback (most recent call last): File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/test_trunk.py",
line 353, in test_list_pagination_page_reverse_with_href_links
self._test_list_pagination_page_reverse_with_href_links() File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1132, in inner return f(self, *args, **kwargs) File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1123, in inner return f(self, *args, **kwargs) File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1346, in _test_list_pagination_page_reverse_with_href_links
self.assertSameOrder(expected_resources, reversed(resources)) File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1160, in assertSameOrder self.assertEqual(len(original), len(actual)) File
"/usr/local/lib/python3.6/dist-packages/testtools/testcase.py", line 411, in
assertEqual self.assertThat(observed, matcher, message) File
"/usr/local/lib/python3.6/dist-packages/testtools/testcase.py", line 498, in
assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 5 != 6
```
Test case 2:
neutron_tempest_plugin.api.test_trunk.TrunksSearchCriteriaTest.test_list_pagination_with_href_links
[id-dcd02a7a-f07e-4d5e-b0ca-b58e48927a9b]
```code
Traceback (most recent call last):
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/test_trunk.py",
line 337, in test_list_pagination_with_href_links
self._test_list_pagination_with_href_links()
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1132, in inner
return f(self, *args, **kwargs)
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1123, in inner
return f(self, *args, **kwargs)
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1312, in _test_list_pagination_with_href_links
self._test_list_pagination_iteratively(self._list_all_with_hrefs)
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1241, in _test_list_pagination_iteratively
len(expected_resources), sort_args
File
"/usr/local/lib/python3.6/dist-packages/neutron_tempest_plugin/api/base.py",
line 1302, in _list_all_with_hrefs
self.assertEqual(1, len(resources_))
File "/usr/local/lib/python3.6/dist-packages/testtools/testcase.py", line
411, in assertEqual
self.assertThat(observed, matcher, message)
File "/usr/local/lib/python3.6/dist-packages/testtools/testcase.py", line
498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 0
```
## Reason for failure:
More neutron trunk ports are being returned than expected.
Code has to be fixed for 2 and 3 below such that trunks are returned
only for one project (specify project_id in GET trunks call). A
parallel test might be creating trunks so this test case is failing.
2. test_list_pagination_page_reverse_with_href_links
-> Expected returns trunks for project: 864acee2d6c64faa8750cfe53437a158
-> Actual paginated returns trunk for more projects:
89e63227c3b6405498f8fb1973cd055d and 864acee2d6c64faa8750cfe53437a158
3. test_list_pagination_with_href_links
Same issue as in 2.
## Able to run the tests if run in serial mode: concurrency = 1
{0}
neutron_tempest_plugin.api.test_networks.NetworksSearchCriteriaTest.test_list_pagination_page_reverse_with_href_links
[3.404399s] ... ok{0}
[Yahoo-eng-team] [Bug 1229445] Re: db type could not be determined
python2.7 and 3.3 are deprecated as well as as testr (there's no .testrepository folder anymore) which was replaced by stestr. The error and the workaround too are not valid anymore. ** Changed in: tempest Status: Incomplete => Invalid -- 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/1229445 Title: db type could not be determined Status in Ironic: Fix Released Status in Magnum: Fix Released Status in OpenStack Compute (nova): Fix Released Status in oslo.versionedobjects: Won't Fix Status in Python client library for Sahara: Invalid Status in tempest: Invalid Status in Testrepository: Triaged Status in Zun: Fix Released Bug description: In openstack/python-novaclient project, run test in py27 env, then run test in py33 env, the following error will stop test: db type could not be determined But, if you run "tox -e py33" fist, then run "tox -e py27", it will be fine, no error. workaround: remove the file in .testrepository/times.dbm, then run py33 test, it will be fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1229445/+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 1760584] Re: IpAddressGenerationFailure warning while running tempest test test_create_subnet_from_pool_with_subnet_cidr
The issue, based on the comments, got resolved in the neutron-tempest- plugin, so from tempest perspective, this can be closed then. I'll mark it as Invalid. If you feel like there is a change needed in tempest, provide info and feel free to reopen it. ** Changed in: tempest Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1760584 Title: IpAddressGenerationFailure warning while running tempest test test_create_subnet_from_pool_with_subnet_cidr Status in neutron: Confirmed Status in tempest: Invalid Bug description: When I run tempest run neutron.tests.tempest.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_subnet_cidr I see below warning in neutron-server Apr 02 08:46:28 test.rdocloud neutron-server[12690]: WARNING neutron.api.rpc.handlers.dhcp_rpc [None req-4bfb3f1d-659f-49b8-8572-c74e7d955731 None None] Action create_port for network 8e90dae6-018e-4979-bfad-2cc96e281ea8 could not complete successfully: No more IP addresses available on network 8e90dae6-018e-4979-bfad-2cc96e281ea8.: IpAddressGenerationFailure: No more IP addresses available on network 8e90dae6-018e-4979-bfad-2cc96e281ea8. This test tries to create a subnet with cidr 10.11.12.0/31 i.e only one address to allocate(which will be taken for gateway_ip). This subnet creation will notify dhcp agent, which will try to create a dhcp port but will fail as there are no address available. Still the subnet create api will be successful as port creation is triggered later from dhcp agent. These tests may fail with vendor's drivers if their implementation try to create dhcp port as part of subnet creation. There is no point in creating a subnet with no IP address. Better to change the tempest tests to provide CIDR with adequate addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1760584/+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 1733498] Re: image.v1.test_image_members failed for “The success code is different than the expected one“
image.v1 is deprecated so I think this bug is not valid anymore.
** Changed in: tempest
Status: New => Invalid
** Changed in: tempest
Assignee: Ghanshyam Mann (ghanshyammann) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1733498
Title:
image.v1.test_image_members failed for “The success code is different
than the expected one“
Status in Glance:
New
Status in tempest:
Invalid
Bug description:
Openstck version: Pike
tempest version: 17.1.0
When I run tempest.api.image.v1.test_image_members.ImageMembersTest,
the test cases failed.
_StringException: pythonlogging:'': {{{
2017-11-21 08:42:38,999 5434 INFO [tempest.lib.common.rest_client]
Request (ImageMembersTest:test_add_image_member): 201 POST
https://10.127.2.30:9292/v1/images 0.659s
2017-11-21 08:42:38,999 5434 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'x-image-meta-container_format': 'bare', 'X-Auth-Token':
'', 'x-image-meta-is_public': 'False', 'Content-Type':
'application/octet-stream', 'x-image-meta-disk_format': 'raw',
'x-image-meta-name': 'tempest-ImageMembersTest-image-608197243'}
Body:
Response - Headers: {'status': '201', u'content-length': '521',
'content-location': 'https://10.127.2.30:9292/v1/images', u'connection':
'close', u'etag': 'fd3e0d53babf78fdc2cdaca026be16b2', u'location':
'https://10.127.2.30:9292/v1/images/59f6c720-37a1-4441-a39f-fdec7a1237e7',
u'date': 'Tue, 21 Nov 2017 00:52:28 GMT', u'content-type': 'application/json',
u'x-openstack-request-id': 'req-661452b2-db33-46a3-8673-5b9c06f9ef04'}
Body: {"image": {"status": "active", "deleted": false,
"container_format": "bare", "min_ram": 0, "updated_at":
"2017-11-21T00:52:28.00", "owner": "db4bbe131a8f458ab3af53e400e5d927",
"min_disk": 0, "is_public": false, "deleted_at": null, "id":
"59f6c720-37a1-4441-a39f-fdec7a1237e7", "size": 1024, "virtual_size": null,
"name": "tempest-ImageMembersTest-image-608197243", "checksum":
"fd3e0d53babf78fdc2cdaca026be16b2", "created_at": "2017-11-21T00:52:27.00",
"disk_format": "raw", "properties": {}, "protected": false}}
2017-11-21 08:42:39,197 5434 INFO [tempest.lib.common.rest_client]
Request (ImageMembersTest:test_add_image_member): 200 PUT
https://10.127.2.30:9292/v1/images/59f6c720-37a1-4441-a39f-fdec7a1237e7/members/6436a595aed34d679cb521da235aa744
0.197s
2017-11-21 08:42:39,197 5434 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json', 'X-Auth-Token': ''}
Body: {"member": {}}
Response - Headers: {'status': '200', u'content-length': '45',
'content-location':
'https://10.127.2.30:9292/v1/images/59f6c720-37a1-4441-a39f-fdec7a1237e7/members/6436a595aed34d679cb521da235aa744',
u'date': 'Tue, 21 Nov 2017 00:52:28 GMT', u'content-type': 'application/json',
u'connection': 'close', u'x-openstack-request-id':
'req-c7e2e557-a40b-4471-8f0f-87d9aa239dec'}
Body: ""
}}}
Traceback (most recent call last):
File
"/home/jenkins/workspace/deploy-manually-test-cd-pm/fitos_test/tests/api_test/tempest/api/image/v1/test_image_members.py",
line 26, in test_add_image_member
self.image_member_client.create_image_member(image, self.alt_tenant_id)
File
"/home/jenkins/workspace/deploy-manually-test-cd-pm/fitos_test/tests/api_test/tempest/lib/services/image/v1/image_members_client.py",
line 53, in create_image_member
self.expected_success(204, resp.status)
File
"/home/jenkins/workspace/deploy-manually-test-cd-pm/fitos_test/tests/api_test/tempest/lib/common/rest_client.py",
line 261, in expected_success
raise exceptions.InvalidHttpSuccessCode(details)
tempest.lib.exceptions.InvalidHttpSuccessCode: The success code is different
than the expected one
Details: Unexpected http success status code 200, The expected status code is
204
So I execute the cmd directly by 'curl'.The result as follow:
[root@cdpm02 ~]# curl -g -i --cacert "/etc/keystone/ssl/ca.crt" -X PUT
https://10.127.2.30:9292/v1/images/1a87cfcb-71c9-4d86-a2ea-0f0bb98fcf1f/members/218030757f8348848e6bdab3eca7cb27
-H "User-Agent: python-glanceclient" -H "Content-Type: application/json" -H
"X-Auth-Token: $token" -d '{"member": {"can_share": false}}'
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 45
X-Openstack-Request-Id: req-0deecacc-1e2f-4dd9-8a02-a7e261839d6a
Date: Tue, 21 Nov 2017 04:14:00 GMT
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1733498/+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 1827489] [NEW] Wrong IPV6 address provided by openstack server create
Public bug reported: IPV6 address of an interface doesn't have to be derived from its MAC address. The newer kernels have addr_gen_mode option which controls the behavior of IPV6 calculation, see https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt I've encountered the problem when I booted up an image (RHEL8 in my case) which had the addr_gen_mode option set to 1 (means that IPV6 address is randomized) by default. OpenStack (I had Rocky deployment) didn't recognize this and 'openstack server create' returned wrong address which lead to tempest failures because thanks to the 'openstack server create' output the tests expected different addresses on the interfaces. Steps to reproduce: $ openstack server create --image --flavor --network --network --key-name instance_name +-++ | Field | Value | +-++ | accessIPv4 | | | accessIPv6 | | | addresses | tempest-network-smoke--884367252=10.100.0.5; tempest-network-smoke--18828977=2003::f816:3eff:febb:7456 | Then ssh to the instance and hit 'ip a' command: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1450 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:48:e8:b5 brd ff:ff:ff:ff:ff:ff inet 10.100.0.3/28 brd 10.100.0.15 scope global dynamic noprefixroute eth0 valid_lft 86363sec preferred_lft 86363sec inet6 fe80::f816:3eff:fe48:e8b5/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1450 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:bb:74:56 brd ff:ff:ff:ff:ff:ff inet6 2003::b47f:f400:ecca:2a55/64 scope global dynamic noprefixroute valid_lft 86385sec preferred_lft 14385sec inet6 fe80::7615:8d57:775d:fae/64 scope link noprefixroute valid_lft forever preferred_lft forever Notice that eth1 interface has an ipv6 address which seems not to be derived from its mac address. Also notice that the output of 'openstack server create' returned wrong address, a different one than it's actually set for eth1. It expected that the ipv6 address would be derived from the mac address but it wasn't. 'openstack server create' should be able to detect the option in the image and behave accordingly. ** 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/1827489 Title: Wrong IPV6 address provided by openstack server create Status in OpenStack Compute (nova): New Bug description: IPV6 address of an interface doesn't have to be derived from its MAC address. The newer kernels have addr_gen_mode option which controls the behavior of IPV6 calculation, see https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt I've encountered the problem when I booted up an image (RHEL8 in my case) which had the addr_gen_mode option set to 1 (means that IPV6 address is randomized) by default. OpenStack (I had Rocky deployment) didn't recognize this and 'openstack server create' returned wrong address which lead to tempest failures because thanks to the 'openstack server create' output the tests expected different addresses on the interfaces. Steps to reproduce: $ openstack server create --image --flavor --network --network --key-name instance_name +-++ | Field | Value | +-++ | accessIPv4 | | | accessIPv6 |
