Bug 2104133 - Need to Backport security group tests "removing security group from ACTIVE instance"
Summary: Need to Backport security group tests "removing security group from ACTIVE i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-neutron-tests-tempest
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ga
: 17.1
Assignee: Slawek Kaplonski
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-05 15:31 UTC by ayenachew molla
Modified: 2023-08-24 14:17 UTC (History)
4 users (show)

Fixed In Version: python-neutron-tests-tempest-2.1.0-1.20230206160927.021ce91.el9ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 01:11:21 UTC
Target Upstream Version:
Embargoed:
skaplons: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 844958 0 None master: MERGED neutron-tempest-plugin: Add a test for removing security group from ACTIVE instance (I9fbcdd0f30beeb6985bab4de4d53af639f... 2022-12-12 18:07:15 UTC
Red Hat Issue Tracker OSP-16251 0 None None None 2022-07-05 16:39:27 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:11:53 UTC

Comment 1 ayenachew molla 2022-07-17 07:28:18 UTC 
Upstream patch - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/844958
Comment 7 Jon Schlueter 2022-08-17 15:19:39 UTC 
Patch is indeed not landed in a build downstream moving back to POST
Comment 24 errata-xmlrpc 2023-08-16 01:11:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577
Note You need to log in before you can comment on or make changes to this bug.