The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "KEDB"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
This page provides a '''central database for Known Errors'''; it collects known errors, namely identified problems/issues for which an underlying cause has been identified already. Known errors are shared on EGI wiki for the following reasons: | |||
*known errors are tracked here for use by HelpDesk team, espacially 1st and 2nd line support, so that known issues can be referenced on new GGUS tickets reporting correlated incidents | *known errors are tracked here for use by HelpDesk team, espacially 1st and 2nd line support, so that known issues can be referenced on new GGUS tickets reporting correlated incidents | ||
| Line 9: | Line 7: | ||
*an ID is provided in order to identify easily the known error | *an ID is provided in order to identify easily the known error | ||
*a quick reference to an incident is always associated to a known error, in order to switch to a concrete example of incident related to the known err<br> | *a quick reference to an incident is always associated to a known error, in order to switch to a concrete example of incident related to the known err<br> | ||
Known errors and workarounds are also provided: | Known errors and workarounds are also provided: | ||
| Line 18: | Line 14: | ||
*by the UMD team in the Release Notes of a specific software release | *by the UMD team in the Release Notes of a specific software release | ||
For these cases, the references are not provided in the Central database for Known Errors and no other central source of information, as aligning the original source and the central replication of information would lead to synchronisation issues and useless information maintenance overload. Instead, references to direct sources are provided below | For these cases, the references are not provided in the Central database for Known Errors and no other central source of information, as aligning the original source and the central replication of information would lead to synchronisation issues and useless information maintenance overload. Instead, references to direct sources are provided below the table | ||
{| width="100%" cellspacing="1" cellpadding=" | {| width="100%" cellspacing="1" cellpadding="10" border="1" align="left" | ||
|+ Known Error DataBase | |||
|- | |- | ||
! scope="col" | ID | ! scope="col" | ID | ||
Revision as of 14:59, 15 October 2016
This page provides a central database for Known Errors; it collects known errors, namely identified problems/issues for which an underlying cause has been identified already. Known errors are shared on EGI wiki for the following reasons:
- known errors are tracked here for use by HelpDesk team, espacially 1st and 2nd line support, so that known issues can be referenced on new GGUS tickets reporting correlated incidents
- the HelpDesk team can suggest new known errors and add them to the shared KEDB and make use of them in case of shifts
- users, VO members, RC/OC operators can be referenced with known errors a slong as they are in use
- workarounds can be referenced/reported together with each known error (the known error will be included in this page even if no workarounds are available yet)
- an ID is provided in order to identify easily the known error
- a quick reference to an incident is always associated to a known error, in order to switch to a concrete example of incident related to the known err
Known errors and workarounds are also provided:
- by Technology Providers in the Release Notes of their products,
- by service providers of EGI in the documentation provided for their services
- by the UMD team in the Release Notes of a specific software release
For these cases, the references are not provided in the Central database for Known Errors and no other central source of information, as aligning the original source and the central replication of information would lead to synchronisation issues and useless information maintenance overload. Instead, references to direct sources are provided below the table
| ID | Title | Context | Description | Impact | Workaround (availability/description) | Link(s) to incident(s) |
|---|---|---|---|---|---|---|
| 1 | canL upgrade can break proxy renewal on CREAM | UMD3/UMD4 | http://repository.egi.eu/2016/09/21/release-umd-4-2-1/ | CREAM service affected, resulting in stopping job submission | remove dracut-fips package | detailed postmortem attached at WLCG meeting agenda, reported by CNAF https://twiki.cern.ch/twiki/bin/view/LCG/WLCGDailyMeetingsWeek161010 |