mysql.service gets masked when upgrading from upstream

Description

When switching from upstream 8.0, once the packages are removed mysql.service gets masked. After PS packages are installed server won't start because of this:

root@xenial:~# service mysql start Failed to start mysql.service: Unit mysql.service is masked.

Unmasking the service resolves the issue:

root@xenial:~# systemctl unmask mysql.service Removed symlink /etc/systemd/system/mysql.service. root@xenial:~# service mysql start root@xenial:~# mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 8 Server version: 8.0.13-3 Percona Server (GPL), Release '3', Revision 'a920dd6'

We should either document this or unmask the service automatically once we install our packages.

Environment

None

Smart Checklist

Activity

Show:

roel.vandepaar December 25, 2018 at 11:18 PM

 thank you very much. I wonder what ran into then.

Does this need further review/input from then?

roel.vandepaar December 24, 2018 at 7:19 AM

 Hrvoje is out, and apparently this happens on 8.0 only. Can you have a look please after your Christmas break? Thank you

Peter Schwaller December 21, 2018 at 1:33 PM

8.0 triage - Hrvoje reports this probably happens on 5.7 as well, but hasn't been able to verify.  This should be filed as an upstream bug (this is incorrect behavior).  Fix if Time.

Cannot Reproduce

Details

Assignee

Reporter

Time tracking

2h 10m logged

Components

Affects versions

Priority

Smart Checklist

Created December 21, 2018 at 11:11 AM
Updated July 22, 2024 at 3:18 PM
Resolved January 20, 2020 at 5:36 PM