Bug 2129359

Summary: Flavor create form should not check for uniqueness of uuid field when its value is auto
Product: Red Hat OpenStack Reporter: Radomir Dopieralski <rdopiera>
Component: python-django-horizonAssignee: Tatiana Ovchinnikova <tovchinn>
Status: CLOSED ERRATA QA Contact: Jan Jasek <jjasek>
Severity: low Docs Contact:
Priority: low    
Version: 17.1 (Wallaby)CC: rdopiera, tovchinn
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-19.4.1-1.20221216084227.d9104a5.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:12:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Radomir Dopieralski 2022-09-23 13:17:50 UTC
Currently the flavor creation form will always check for the uniqueness of the UUID field, even when it is set to "auto". That means that if we create a flavor with UUID value of "auto", the check will fail. We should disable the check when UUID is automatically generated.

Comment 13 errata-xmlrpc 2023-08-16 01:12:16 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