Please login to properly see the content of this page. You need to be logged in Jira at least once in order to see the details of the Jira exctracts of this page.

General overview

This is the EGI Federation Known Errors Database created with the purpose to track known errors affecting the middleware deployed in the EGI Infrastructure. According to FITSM definition, a Known Error is a problem which has not (yet) been corrected, but for which there is a documented workaround or temporary fix to prevent (excessive) negative impact on service.

The information available in the KEDB is useful for:

• the support teams of the EGI Helpdesk service,  especially 1st and 2nd line support, that can use it as reference while investigating on new GGUS tickets reporting correlated incidents.
• users, VO members, RCs administrators, NGI operators that can use it to find a solution to any similar issues before opening a related incident ticket.

This page can host also errors whose root cause is known, but no workaround is available yet, in order to proactively provide a reference to the EGI Helpdesk support teams.

Known errors and corresponding workarounds are also provided:

• by Technology Providers in the Release Notes of their products,
• by service providers that are part of EGI in the documentation provided for their services

When a Known Error is identified, a corresponding Jira ticket is created to report it and track its evolution. The Known Errors are flagged as:

• OPEN, if no workarounds are available and no solution is provided (ticket status: new, and "in progress");
• WORKAROUND, If workaround/mitigation is in place, but no solution has been provided yet;
• SOLVED, If solution is provided;
• UNSOLVED, if the solution will not be provided but there is a workaround available.