Bug 1986620 - Backport the test to verify FQDN hostname sanitization
Summary: Backport the test to verify FQDN hostname sanitization
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 16.2 (Train on RHEL 8.4)
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-27 22:02 UTC by Martin Kopec
Modified: 2022-03-23 22:11 UTC (History)
8 users (show)

Fixed In Version: openstack-tempest-26.1.0-2.20211013134917.271f820.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-23 22:10:49 UTC
Target Upstream Version:
Embargoed:
chkumar: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 795699 0 None MERGED Add test to verify FQDN hostname sanitization 2021-07-27 22:03:14 UTC
Red Hat Issue Tracker OSP-6479 0 None None None 2021-11-15 13:02:41 UTC
Red Hat Product Errata RHBA-2022:1001 0 None None None 2022-03-23 22:11:20 UTC

Description Martin Kopec 2021-07-27 22:02:51 UTC 
Tempest upstream patch needs to be backported:
https://review.opendev.org/c/openstack/tempest/+/795699
Comment 8 Martin Kopec 2022-02-01 10:28:14 UTC 
Fixed in version package openstack-tempest-26.1.0-2.20211013134917.271f820.el8ost contains the fix - necessary change which was meant to be backported - and the package is part of RHOS-16.2-RHEL-8-20220125.n.2 puddle -> VERIFIED
Comment 14 errata-xmlrpc 2022-03-23 22:10:49 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 16.2.2), 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/RHBA-2022:1001
Note You need to log in before you can comment on or make changes to this bug.