neutron_tempest_plugin.api.test_subnets.SubnetServiceTypeTestJSON.test_allocate_ips_are_from_correct_subnet fails with Unrecognized attribute(s) 'service_types'

Bug #1933115 reported by Ananya Banerjee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

neutron_tempest_plugin.api.test_subnets.SubnetServiceTypeTestJSON fails with

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/neutron_tempest_plugin/api/test_subnets.py", line 91, in test_allocate_ips_are_from_correct_subnet
    cidr=str(cidr_1))
  File "/usr/lib/python3.6/site-packages/neutron_tempest_plugin/api/base.py", line 465, in create_subnet
    **kwargs)
  File "/usr/lib/python3.6/site-packages/neutron_tempest_plugin/services/network/json/network_client.py", line 145, in _create
    resp, body = self.post(uri, post_data)
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py", line 299, in post
    return self.request('POST', url, extra_headers, headers, body, chunked)
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py", line 703, in request
    self._error_checker(resp, resp_body)
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py", line 814, in _error_checker
    raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {'type': 'HTTPBadRequest', 'message': "Unrecognized attribute(s) 'service_types'", 'detail': ''}

https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master/be01c1e/logs/undercloud/var/log/tempest/stestr_results.html.gz

https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master/446d107/logs/undercloud/var/log/tempest/stestr_results.html.gz

Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
milestone: none → xena-1
tags: added: promotion-blocker
wes hayutin (weshayutin)
summary: - neutron_tempest_plugin.api.test_subnets.SubnetServiceTypeTestJSON
+ neutron_tempest_plugin.api.test_subnets.SubnetServiceTypeTestJSON.test_allocate_ips_are_from_correct_subnet
fails with Unrecognized attribute(s) 'service_types'
description: updated
Revision history for this message
Marios Andreou (marios-b) wrote :

don't know why it wasn't picked up by the bots but as a temporary measure the test was added to skiplist with https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/797320

Changed in tripleo:
milestone: xena-1 → xena-2
Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :
Revision history for this message
Marios Andreou (marios-b) wrote :
Revision history for this message
Marios Andreou (marios-b) wrote :
Revision history for this message
Marios Andreou (marios-b) wrote :

so the fix at comment #4 actually causes the skip to happen now with a green run there https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/798068/1#message-3e4207c2cb50bff233534ffb0bdc9862bdc03f16

I am just uncomfortable skipping these tests. Does this mean we are promoting broken content?

Thinking about it a bit i guess the key thing is for this same issue to block the relevant component. In this case possibly networking for example. i.e. networking component line will only give us new content when it is working again since it is broken/blocked on the same issue. . so in the meantime it is not relevant for the integration line we are 'locked' on the older component content until it is fixed and can promote again.

Revision history for this message
wes hayutin (weshayutin) wrote :

RE:
I am just uncomfortable skipping these tests. Does this mean we are promoting broken content?

The process is that we can promote builds with failing tempest tests as long as we have the CIX logged. We can not hold builds for any tempest test. If you feel this particular test is critical enough to hold the build, then we can have the conversation.

Looking at
https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master/f154efc/logs/undercloud/var/log/tempest/stestr_results.html.gz

I would strongly suggest that we do NOT hold the build for these results:
Status: Pass 1419 Failure 1 Skip 149

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

@Marios: in this specific case, that was more issue with Neutron API extensions which I enabled/disabled for OVN backend and it should be fixed soon with https://review.opendev.org/c/openstack/neutron/+/797595
So for now skipping this test is valid workaround for me as that is what actually should be done when this API extension isn't available.

Revision history for this message
chandan kumar (chkumar246) wrote :

https://review.opendev.org/c/openstack/neutron/+/797595 is merged now. It is tested here
https://review.rdoproject.org/r/c/testproject/+/34332

- https://logserver.rdoproject.org/32/34332/1/check/periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master/9cda58e/logs/undercloud/var/log/tempest/tempest_run.log.txt.gz

```
{2} setUpClass (neutron_tempest_plugin.api.test_subnets.SubnetServiceTypeTestJSON) ... SKIPPED: subnet-service-types extension not enabled.
```

I think we can close this bug with fix released.

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

It should be fixed in Neutron now with https://review.opendev.org/c/openstack/neutron/+/797595

Changed in tripleo:
milestone: xena-2 → xena-3
Revision history for this message
Ronelle Landy (rlandy) wrote :

entry is no longer in the skiplist - closing out

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.