Bug 502199
Summary: | Duplicate versions in SEP+ validation needed to prevent in future | |||
---|---|---|---|---|
Product: | [Retired] JBoss Customer Support Portal | Reporter: | Tom Mirc <tmirc> | |
Component: | SEP | Assignee: | JBoss CSP Bug Watch List <csp-bugs-watch> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | MR12 | CC: | dspaldin, gshipley, nyancey, rbroadna, vkumar | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 513061 (view as bug list) | Environment: | ||
Last Closed: | 2009-07-27 12:42:15 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 507385, 513061 |
Description
Tom Mirc
2009-05-22 14:37:26 UTC
I need AM team to: 1) Consolidate the 4 above referenced Software listings to 2. (Delete 331 and 332, leaving only 334 and 337). 2) Determine a technical solution that prevents creation of duplicate downloads. In this case, the base download for EAP 4.2.0 CP_06 is duplicated, and both downloads are mapped to JBoss ON version 4.0. They were likely create by two different members of Support Engineering. The fields Product Category and Version could be combined and transformed into a validation rule so that duplicate software downloads are not allowed in SEP. Id: 334 Software Id: SOFT-10334 Name: Application Platform Version: 4.2.0.GA_CP06 Product Category: appplatform Module: Created: Fri Feb 27 2009 18:35:47 GMT-0500 (EST) Last Modified: Fri Feb 27 2009 18:36:18 GMT-0500 (EST) JBoss ON JON Resource Type: JBoss 4.0 JON Resource Version: 4.2.0.GA_CP06_EA Moving to XPlanner backlog. verified in development/am-qa. Ready for testing in stage. Developer will add comments to explain how the solution being implemented will be rolled-out to prevent future duplicates and the cleanup of duplicate records. Use Issue Tracker login to access https://support.stage.redhat.com/support-portal/login.html Found 334 and 337 deleted in Stage, only 331 and 332 remaining. https://support.stage.redhat.com/support-portal/restricted/software/softwareDetails.html?id=331 https://support.stage.redhat.com/support-portal/restricted/software/softwareDetails.html?id=332 from comment #1 above, 1) has been accomplished. Will clone this bug for the 2) item, preventing further duplications. Here is the List of the duplicate items in prod enviornment :- These are the software Id's in software table. 1)1 - 30 - 41 2)26 -42 - 34 - 46 - 155 3)44- 130 4)55 - 343 5)68 - 76 6)88 - 200 7)107 - 126 - 203 8)106 - 159 9)215 - 217 10)219 - 313 11)263 - 281 12)283 - 287 13)307 - 309 14)310 - 311 15)331- 334 16)332 - 337 17)357 - 358 - 359 and these are software Ids I have deleted :- 30, 41 , 42 , 34 , 46 , 155 , 44,343, 76,88,107, 203 , 159 , 217 ,219 , 263, 287 , 307 , 310 , 337, 334 , 358 , 359 And software_name column from software table is associated with software column of repository table . So whenever any software item is deleted , the corresponding association in repository table has to be pointed to the other software item which we have kept intact after deleting the duplicate one . Released to Production 7/25 |