FUJ00176330
FUJ00176330
Peak Incident Management System
Call Reference PC0206479 Call Logger Deleted User -- QC Interface
Release Targeted At -- HNG-X 03.13 Top Ref AUDIT EXTRACT CLT_0313_D064-D063
Call Type Quality Centre Raised Incidents/Defects Priority B -- Medium Impact - Priority 3
Contact Deleted Contact Call Status Closed -- S/W Fix Available to Call Logger
Target Date 25/11/2010 Effort (Man Days) 0
Summary LST RO03.13 - Audit Extractor incorrectly reports all JSNs as duplicates for Node 2
All References Type Value
DevIntRel-Director QC Interface
QC Defect No 14462
Product Baseline AUDIT_EXTRACT_CLT_0313_V064
QC_DEFECTID 14462-hng x _hng x release _1 db.
Product Baseline AUDIT_EXTRACT_CLT_0313_D064-D063
Release PEAK PC0206620
Product Baseline AUDIT_EXTRACT_CLT_0313_V064-V063
QC Severity 3 - High
Iny
Si eee User Date I
Unknown 22-Nov-2010 17:45:55
The Audit Client application can incorrectly report duplicate messages on the Sequence Validation tab of
the "slow ARQ" interface when there are no duplicate mesages present.
Progress Narrative
[Date:18-Nov-2010 10:30:06 User:John Rogers
CALL Pc0206479 opened
Details entered are:~
Summary:LST RO3.13 - Audit Extractor incorrectly reports all JSNs as duplicates for Node 2
all Type:0
call Priority:B
target Relea LST 03.13
Routed to:QFP - Unassigned_
JDate:18-Nov-2010 10:30:06 Uscr:John Rogers
ee eteeeteeresereesert+ Quality Centre Bug Report *#+4tttrittereeeees
lBug Reference: 14462-hng _x_hng x release 1 db.
fest Date: Nov 18 2010 12:00AM
lest User: rogers}
loc Impact: 3 - High
Pathcode: Path201
joTI Team: None
Product: Infrastructure
product. Version: N/A
Summary: LST RO3.13 - Audit Extractor incorrectly reports all JSNs as duplicates for Node 2
incident Description:
lA new Slow ARQ was created to retrieve Audit Tracks for FAD 015010 which is a 2 counter outlet.
tn the “Validation and Query" tab all the JSNs for Node 2 are reported as being duplicates, see attached screen print.
It checked retrieved files for a few of the JSN's and could not find any duplicates, attached is a zipped copy of the EXTRACTED AT
folder with the Audit Tracks renamed from .audgz to .txt to allow the Windows search to be used.
iowever, this only seems to be a display problem as an output spreadsheet (from Hx IOP query) is reporting that there are no
duplicates.
comments:
[john Rogers <rogersj>, 18/11/2010 10:21:29:
impact
[fhe Audit Workstation u
instruction to "SEEK AS:
x is given an incorrect view of the existance of duplicate JSNs in the retrieved data, and an
STANCE FROM AUDIT SUPPORT".
ohn Rogers <rogersj>, 18/11/2010 10:22:37:
Please route call to Audit Dev
FUJ00176330
FUJ00176330
fDate:18-Nov-2010 10:30:11 User:gohn Rogers
levidence imported from QC - BUG 14462 EXTRACTED AT.zip
evidence imported from QC - BUG 14462 Duplicates.zip
Evidence imported from QC - BUG 14462_HxIOP.xls
jbate:18-Nov-2010 10:53:07 User:Lionel Higman
the Call record has been transferred to the team: Audit-Dev
JDate:18-Nov-2010 15:16:23 User:Andrew Mansfield
[the Call record has been assigned to the Team Member: Andrew Mansfield
Jbate:19-Nov-2010 1:
comments Update:
0:06 User:John Rogers
Sohn Rogers <rogersj>, 19/11/2010 11:01:44:
[two further problems have been found which appear to be related to this problem. If this is not the case then I'm happy to raise
jadditional PEAKs.
lin the retrieved files I believe there are no Duplicates and the GAPS should be
076137 Node 1 - 63471 to 63492
Jo76137 Node 2 - 9423 to 9443
h) ARQ OTH3566B (Filtered on two multi-counter FADS, 076137 and 017632)
Validation and Query" screen displays "GAPS FOUND" but nothing is highlighted in Red.
the actual gaps are shown in Blue.
However, the majority of entries, including some for Node 1 are also shown in Blue.
2) ARO OTH3567B (Filtered on one multi-counter FAD 076137)
[fhe GAP in the Node 2 transaction sequences is high-light in Blue not Red.
lattached are zipped files foe each of the ARQs.
evidence imported from QC - BUG 14462 OTH3566B.zip
Evidence imported from QC - BUG 14462 OTH3567B.zip
[Date:22-Nov-2010 09:39:11 User:John Budworth
[fhe call Target Release has been moved to Targeted At -~ HNG-X 03.13
[bate:22-Nov-2010 1°
Invidence Added - 1
2:16 User:Andrew Mansfield
jDate:22-Nov-2010 17:43:35 User:Andrew Mansfield
Product HNG-X Platforms -- Audit Workstation (AUW) (version unspecified) added.
JDate:22-Nov-2010 17:45:55 User:Andrew Mansfield
lA new Business Impact has been addé
the Audit Client application can incorrectly report duplicate messages on the Sequence Validation tab of the ‘slow ARQ" interface
lshen there are no duplicate mesages present.
bate: 22-Nov-2010 17:58:37 User:Andrew Mansfield
[Start of Response]
[fhe problem arises when the message sequence numbers for a particular node number are lower than the message sequence numbers for
Js lower numbered node (for the same FAD code).
iere's an example from the attached evidence:
153125 153213
42848 42848
42849 42853
the two rows for node 4 are incorrectly marked as duplicates because they are being compared against the node 1 row.
the fix was tested by running filters against the message files supplied as evidence and checking that gaps and duplicates are
correctly highlighted.
[End of Response]
esponse code to call type Q as Category 40 -- Pending -- Incident Under Investigation
jbate:22-Nov-2010 18:35:11 Uscr:Andrew Mansfield
Reference Added: Product Baseline AUDIT_EXTRACT_CLT_0313_vo064
IDate:22-Nov-2010 18:36:24 User:Andrew Mansfield
Reference Deleted: Product Baseline AUDIT EXTRACT CLT 0313 voe4
jbate:22-Nov-2010 18:41:03 User:Andrew Mansfield
FUJ00176330
FUJ00176330
[Start of Responsel
Fixed by incremental baseline AUDIT EXTRACT CLT _0313_v064-V063.
[End of Response]
lkesponse code to call type Q as Category 48 -- Pending -- Fix Released to PIT
jbate:22-Nov-2010 18:41:09 Uscr:Andrew Mansfield
Defect cause updated to 14: Development - Code
JDate:22-Nov-2010 18:41:20 User:Andrew Mansfield
[the Call record has been transferred to the team: Dev-Int-Rel
jbate:23-Nov-2010 09:47:16 User:PIT Automated User
[Start of Response]
ssigning to Integrator
[End of Response]
lkesponse code to call type Q as Category 48 (Fix Released to PIT)
[the incident has been transferred to the Team: Dev-Int-Rel
the incident has been assigned to the Team Member: Geoff Inglis
Date:23-Nov-2010 12:47:15 User:PIT Automated User
[Start of Response]
Peak has been test installed in Integration. Moving to holding stack awaiting release
[End of Response]
esponse code to call type Q as Category 47 (Fix Processed by PIT)
[the incident has been transferred to the Team: Int-Rel
IDate: 23-Nov-2010 13:02:09 User:PIT Automated User
[Start of Response]
Peak has been test installed in integration, routing back to source.
[End of Response]
response code to call type Q as Category 60 (S/W Fix Available to Call Logger)
lfarget Date updated: new value is 25/11/2010 18:30
kouting to Call Logger following Final Progress update.
pat
lkeference Added:
38-Nov-2010 16:23:20 User:Victoria Hancock
lDate:25-Nov-2010 15:15:12 User:dohn Rogers
Incident closure received from Quality Centre
comments Update:
John Rogers <rogersj>, 25/11/2010 14:36:40:
cleared in Release 3.13 (Audit System) and tested in LST under Release Notes BRU7206 and HRU7239.
closing call
Jat e:25-Nov-2010 15:15:12 User:John Rogers
CALL PC0206479 closed: Category 60 Type Q
Root Cause Development - Code
Logger Deleted User -- QC Interface
Subject Product QC Defects -- Infrastructure (version: 1)
Assignee Deleted User -- QC Interface
Last Progress 25-Nov-2010 15:15 -- John Rogers