How to Add the Instance to Bugzilla

 

Once you have found the cause of the core in Bugzilla and there is a workaround or resolution provided in a PTR (bug), you will need to apply the workaround and add this occurrence to the PTR. In addition, each time a new customer is associated with a  PTR, you need to make sure that the external customer name, Service Request number, and other details are included in a new PTR comment.

 

If the workaround doesn't work, you will then need to escalate this issue to SES and will not need to add the information to Bugzilla at this time.

 


 

Complete the following steps to add the instance to Bugzilla:

 

  1. Go to http://bugzilla.quantum.com/bugzilla/ Link will open in new window. and log in.

     

  2. Search for the relevant PTR.

     

  3. On the PTR page, enter the following information:

     

    • Add the customer name to the External Customer Name field
    • Add the Service Request number to the External Ticket Number field

 

  1. In the Additional Comments field, make sure to also enter the following information: (an example displays at the end of this topic) 

     

    • Customer Name
    • Quantum SR
    • [If Fujitsu / EMC] OEM ticket number
    • Exact Platform (For example, not just "6500." A good example would be "SYSTEM BASE, 20TB, RACK, DOMESTIC, DXI8500." Find the information in the scratch/collect/node1-collection/app-info/systemconfig.txt file and not in the collect.txt
    • Software Version (For example, 1.4.4_85)
    • Impact to the Customer
    • Log location  (Note: please make location in the form of http://susrepo/ticketinfo/SR13xxxxx/SR138xxxx/SRXXXXXXX_Customer/ so that people without raptor access can get the files as well.)
    • Output of logs

       

     

  1. Click Save Changes. 

Note: Once the changes have been saved they can not be changed so please verify your notes. 

 

  1. Update the Service Request in Oracle to reflect this PTR.

     

  2. Open the Workbench Flex Fields in Oracle. To access these fields, click the box located immediately to the right of the Problem Code field in the following image.

 

  1. Add the PTR number to the Root Cause BUG Number field.
  1. If this issue is fixed in a future firmware then you will need to add that to the Fixed in Future Firmware field. 

     

  2. Click OK

     

  3. In the Workbench, create a new Note stating that this has been added to the PTR.

     

  4. Save your changes. 

Example

The following section shows an example of a completed Additonal Comments field in Bugzilla.

 

Customer name:  Customer

Quantum SR:  1XXXXXX

Exact Platform:  SYSTEM BASE,20TB,RACK,DOMESTIC,DXI8500

Model:  DXi8500

Vendor:  Quantum

SW Version:  1.4.4_85

Base OS Version:  1.4.4_85-5875

Firmware Version:  1.4.4_85-41904

Linux version:  2.6.18-164.15.1.qtm.4

System S/N:  CX1125BVFXXXXX

Impact to the Customer:  DXi8500 seeing a winbindd core RAS ticket.  This caused the system to shut down which led to a Blockpool Verify.  A RAS ticket was found on the GUI as well.

 

 

Logs location:  http://susrepo/ticketinfo/SR13xxxxx/SR138xxxx/SRXXXXXXX_Customer/

 

tsunami:

 

INFO   - 04/11/12-05:02:12 - healthcheck HCIntegrityCheckThread.cpp(465) [healthcheck] doProcess() - {1106848096} Integrity healthcheck complete

INFO   - 04/11/12-05:02:16 - healthcheck Bfst.cpp(910) [healthcheck] disconnect() - RemoteBfst::disconnect bfst_disconnect '127.0.0.1'

WARN   - 04/11/12-09:47:54 - Seer Seer.cpp(248) [webguid] GetStringValue() - Item 'Value' has no value

INFO   - 04/11/12-09:48:04 - hwmon perfmon.cpp(750) [hwmon] ReadClientConnection() - Got subscription/renewal from client '127.0.0.1', period 60 seconds, flags 0x1

WARN   - 04/11/12-09:48:04 - hwmon perfmon.cpp(650) [hwmon] PerfServerThread() - Setting perfmon loop interval to 1 second

INFO   - 04/11/12-09:49:04 - hwmon perfmon.cpp(286) [hwmon] loop_action() - Subscription ended for client '127.0.0.1'

WARN   - 04/11/12-09:49:04 - hwmon perfmon.cpp(650) [hwmon] PerfServerThread() - Setting perfmon loop interval to 3600 second

 

messages:

 

 

 

Apr 10 16:49:47 som-dxi01 heartbeat: [21803]: info: MSG stats: 0/0 ms age 7145364270 [pid21809/HBREAD] Apr 10 16:49:47 som-dxi01 heartbeat: [21803]: info: ha_malloc stats: 385/6273248  62684/34611 [pid21809/HBREAD] Apr 10 16:49:47 som-dxi01 heartbeat: [21803]: info: RealMalloc stats: 63152 total malloc bytes. pid [21809/HBREAD] Apr 10 16:49:47 som-dxi01 heartbeat: [21803]: info: Current arena value: 0 Apr 10 16:49:47 som-dxi01 heartbeat: [21803]: info: These are nothing to worry about.

 

 

 

 

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.839168,  0] lib/fault.c:46(fault_report)

 

 

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.839317,  0] lib/fault.c:47(fault_report)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   INTERNAL ERROR: Signal 11 in pid 17888 (3.5.2-qtm.8)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   Please read the Trouble-Shooting section of the Samba3-HOWTO

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.839369,  0] lib/fault.c:49(fault_report)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.839415,  0] lib/fault.c:50(fault_report)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   ===============================================================

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.839449,  0] lib/util.c:1465(smb_panic)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   PANIC (pid 17888): internal error

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.870985,  0] lib/util.c:1569(log_stack_trace)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   BACKTRACE: 31 stack frames:

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #0 winbindd(log_stack_trace+0x1c) [0x2b26540de814]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #1 winbindd(smb_panic+0x7e) [0x2b26540de66a]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #2 winbindd [0x2b26540c6d19]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #3 winbindd [0x2b26540c6d2c]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #4 /lib64/tls/libc.so.6 [0x2b26559492b0]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #5 /lib64/tls/libc.so.6(memset+0x60) [0x2b265598c7f0]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #6 /usr/lib64/libkrb5.so.3(krb5_mk_ncred+0x5de) [0x2b265525fc0e]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #7 /usr/lib64/libkrb5.so.3(krb5_mk_1cred+0x68) [0x2b265525fcc8]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #8 /usr/lib64/libkrb5.so.3(krb5_fwd_tgt_creds+0x43e) [0x2b2655258efe]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #9 winbindd [0x2b2654138cee]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #10 winbindd [0x2b26541370ec]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #11 winbindd(cli_krb5_get_ticket+0x2aa) [0x2b2654137576]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #12 winbindd(spnego_gen_negTokenTarg+0x88) [0x2b265413a3a7]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #13 winbindd [0x2b2654124fad]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #14 winbindd(cli_session_setup_spnego+0x96f) [0x2b26541260e4]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #15 winbindd [0x2b2653fe3d8e]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #16 winbindd [0x2b2653fe5c86]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #17 winbindd [0x2b2653fe60c9]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #18 winbindd(init_dc_connection+0x3e) [0x2b2653fe6131]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #19 winbindd [0x2b2653fe614e]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #20 winbindd(cm_connect_netlogon+0x33) [0x2b2653fe81f3]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #21 winbindd [0x2b2653fe3227]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #22 winbindd [0x2b2653fe4ea6]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #23 winbindd [0x2b2653fe2397]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #24 winbindd [0x2b2653fe2628]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #25 winbindd(run_events+0x205) [0x2b26540f4c27]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #26 winbindd [0x2b26540f5039]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #27 winbindd(_tevent_loop_once+0xcb) [0x2b26540f6028]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #28 winbindd(main+0xb5a) [0x2b2653fc75a6]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #29 /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x2b26559373fb]

Apr 11 09:00:09 som-dxi01 winbindd[17888]:    #30 winbindd [0x2b2653fc450a]

Apr 11 09:00:09 som-dxi01 winbindd[17888]: [2012/04/11 09:00:09.877382,  0] lib/fault.c:326(dump_core)

Apr 11 09:00:09 som-dxi01 winbindd[17888]:   dumping core in /var/log/samba/cores/winbindd

Apr 11 09:00:09 som-dxi01 winbindd[17888]:

Apr 11 09:01:03 som-dxi01 srvclogcli: E0000(1)<1010293776>:SRVCLOG RCOMP: 66 RINST: trimcores VCOMP: 66 VINST: UNKNOWN VPINST: UNKNOWN EVENT: 51 TEXT: New core file:-rw-------  1 root root 3784704 Apr 11 09:00 /scratch/core/winbindd-1334149209-17888 

 

 

 

 

Gdb

Thread 1 (process 17888):

#0  0x00002b265594921d in raise () from /lib64/tls/libc.so.6

#1  0x00002b265594aa1e in abort () from /lib64/tls/libc.so.6

#2  0x00002b26540c7457 in dump_core () from /scratch/SR1408236/winbindd

#3  0x00002b26540de7f8 in smb_panic () from /scratch/SR1408236/winbindd

#4  0x00002b26540c6d19 in fault_report () from /scratch/SR1408236/winbindd

#5  0x00002b26540c6d2c in sig_fault () from /scratch/SR1408236/winbindd

#6  <signal handler called>

#7  0x00002b265598c7f0 in memset () from /lib64/tls/libc.so.6

#8  0x00002b265525fc0e in krb5_mk_ncred () from /usr/lib64/libkrb5.so.3

#9  0x00002b265525fcc8 in krb5_mk_1cred () from /usr/lib64/libkrb5.so.3

#10 0x00002b2655258efe in krb5_fwd_tgt_creds () from /usr/lib64/libkrb5.so.3

#11 0x00002b2654138cee in ads_krb5_get_fwd_ticket () from /scratch/SR1408236/winbindd

#12 0x00002b26541370ec in ads_krb5_mk_req () from /scratch/SR1408236/winbindd

#13 0x00002b2654137576 in cli_krb5_get_ticket () from /scratch/SR1408236/winbindd

#14 0x00002b265413a3a7 in spnego_gen_negTokenTarg () from /scratch/SR1408236/winbindd

#15 0x00002b2654124fad in cli_session_setup_kerberos () from /scratch/SR1408236/winbindd

#16 0x00002b26541260e4 in cli_session_setup_spnego () from /scratch/SR1408236/winbindd

#17 0x00002b2653fe3d8e in cm_prepare_connection () from /scratch/SR1408236/winbindd

#18 0x00002b2653fe5c86 in cm_open_connection () from /scratch/SR1408236/winbindd

#19 0x00002b2653fe60c9 in init_dc_connection_network () from /scratch/SR1408236/winbindd

#20 0x00002b2653fe6131 in init_dc_connection () from /scratch/SR1408236/winbindd

#21 0x00002b2653fe614e in init_dc_connection_rpc () from /scratch/SR1408236/winbindd

#22 0x00002b2653fe81f3 in cm_connect_netlogon () from /scratch/SR1408236/winbindd

#23 0x00002b2653fe3227 in get_dc_name_via_netlogon () from /scratch/SR1408236/winbindd

#24 0x00002b2653fe4ea6 in get_dcs () from /scratch/SR1408236/winbindd

#25 0x00002b2653fe2397 in fork_child_dc_connect () from /scratch/SR1408236/winbindd

#26 0x00002b2653fe2628 in check_domain_online_handler () from /scratch/SR1408236/winbindd

#27 0x00002b26540f4c27 in run_events () from /scratch/SR1408236/winbindd

#28 0x00002b26540f5039 in s3_event_loop_once () from /scratch/SR1408236/winbindd

#29 0x00002b26540f6028 in _tevent_loop_once () from /scratch/SR1408236/winbindd

#30 0x00002b2653fc75a6 in main () from /scratch/SR1408236/winbindd

 



This page was generated by the BrainKeeper Enterprise Wiki, © 2018