Yum/RPM upgrade of PS 5.7 re-enables mysql.service when it was disabled
Bug #1709811 reported by
EvgeniyPatlan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.7 |
Fix Released
|
Undecided
|
EvgeniyPatlan | |||
Bug Description
The latest 5.7 PS seems to re-enable the 'mysql.service' every time a yum upgrade is ran, even when the service was disabled manually in systemd via 'systemctl disable mysql'.
The term 'disabled' and 'enabled' in systemd determines whether or not a service is started on startup/reboot.
I'm seeing this problem on version: Percona-
The desired behaviour I expected is if the 'mysql.service' is disabled in systemd, the Yum/RPM upgrade would maintain the disabled state and NOT enable the service. However, currently each time I upgrade the 'mysql.service' is enabled again.
Revision history for this message
| EvgeniyPatlan (evgeniy-patlan) wrote | #1 |
| Changed in percona-server: | |
| status: | New → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
https:/