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"
| Line 23: | Line 23: | ||
! scope="col" | Title | ! scope="col" | Title | ||
! scope="col" | Context | ! scope="col" | Context | ||
! scope="col" | Description | ! scope="col" | Description | ||
! scope="col" | References | ! scope="col" | References | ||
! scope="col" | Impact | ! scope="col" | Impact | ||
Revision as of 22:03, 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.
| Creation date (YYYY/MM/DD) | ID | Title | Context | Description | References | Impact | Workaround (availability/description) |
|---|---|---|---|---|---|---|---|
| 2016-06-29 | 1 | umd-release-3.0.1 rpm has stopped working, preventing new installation of the UMD3 middleware |
UMD3/UMD4 | umd-release packaged, used for adding the UMD3 repository to an existing installation, is not working anymore | Ticket: https://ggus.eu/?mode=ticket_info&ticket_id=122424 | High - whoever try to install a new service from UMD3 is affected | yum can be invoked with the "--nogpgcheck" |
| 2016-10-10 | 2 | canL upgrade of UMD 3.14.4 and UMD 4.2.1 can break proxy renewal on CREAM | UMD3/UMD4 | CREAM services can stop submitting jobs using proxy renewal |
|
Low (very particular OS setup with installation of dracut is needed) | remove dracut-fips package |