Bug 1598173
| Summary: | mariadb no longer reads /etc/mysql/my.cnf | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karel Volný <kvolny> | |
| Component: | mariadb | Assignee: | Michal Schorm <mschorm> | |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 28 | CC: | dciabrin, hhorak, jstanek, mbayer, mkocka, mmuzila, mschorm, praiskup | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1598174 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-28 22:02:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1598174 | |||
|
Description
Karel Volný
2018-07-04 14:26:13 UTC
So far it seems to me like an expected change introduced by the upstream. They just haven't update their KB articles yet. I'll ask the upstream specifically to make this clear. Is that any problem for the users? (In reply to Michal Schorm from comment #1) > Is that any problem for the users? tricky question :-) it might be better answered by some support representative, however, from my experience, any changes in things that "just worked" for ages are always a problem, especially without any apparent reason for the change and without proper documentation Upstream issue tracker created: https://jira.mariadb.org/browse/MDEV-16879 Upstream documents those directories here: https://mariadb.com/kb/en/library/configuring-mariadb-with-mycnf/ so our packages are according to the RPM part there. The original idea of the patches in https://jira.mariadb.org/browse/MDEV-6485 was to not hard-code the paths, but only use the CMAKE-configured paths for the my.cnf. Removing /etc/mysql/my.cnf was not the intention, I'd maybe call it even an incomplete patch, and it would probably be ok to include also "DEFAULT_SYSCONFDIR+/mysql". Anyway, since for our distros (Fedora, RHEL, CentOS), the path /etc/mysql/my.cnf was never used, and for non-RPM distros the /etc/mysql/my.cnf still works (according to https://mariadb.com/kb/en/library/configuring-mariadb-with-mycnf/), I don't consider it a real problem for users and we should be fine to keep it as it is. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |