Bug 1173362 - Check for existing OSMajor when setting alias
Summary: Check for existing OSMajor when setting alias
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 19.2
Assignee: Dan Callaghan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-11 23:20 UTC by Amit Saha
Modified: 2018-02-06 00:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-20 03:18:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Amit Saha 2014-12-11 23:20:22 UTC
Description of problem:

Fix for bug 907242 prevented importing distros with osmajor matching an existing alias. However, the reverse is still allowed, but should not be. It  breaks operations in other parts of the server such as in adding a task to the task library.

The fix for this bug will not allow setting an alias which already matches an existing osmajor.


Version-Release number of selected component (if applicable):

19.1


How reproducible:

Always.


Steps to Reproduce:
1. Go to the Admin -> OS Versions page
2. Click on any OSMajor
3. Add an alias which is the same as any other existing OSMajor
4. Alias is successfully set

Actual results:

(4) above.

Expected results:

The fix for this bug will not allow setting an alias which already matches an existing osmajor.

Additional info:

Comment 1 Dan Callaghan 2014-12-12 00:18:29 UTC
The other problem we must fix as part of this is that the form currently accepts empty string and stores that. Clearing the alias should store NULL instead.

Believe it or not, "" is a valid OS major and it even exists in our Beaker installation, so storing "" for the alias will still be a duplicate.

Comment 2 Dan Callaghan 2015-01-07 05:02:29 UTC
http://gerrit.beaker-project.org/3898

Comment 5 Dan Callaghan 2015-01-20 03:18:48 UTC
Beaker 19.2 has been released.


Note You need to log in before you can comment on or make changes to this bug.