This seems to be yet a different issue. In order to try to reproduce the problem you faced we need at least to know the following things:
- Which version were you upgrading *from*?
- Was the upgrade part of a release-upgrade to Eoan?
- How exactly did you reconfigure AppArmor to allow
the mysql datadir to be in a location different
from /var/lib/mysql?
Anyway I attempted to reproduce in an upgrade from Disco (mysql-server 5.7.27-0ubuntu0.19.04.1) to Eoan (mysql-server 5.7.27-0ubuntu2) and wasn't able to. My alternate datadir was /mysql, and I added the following line:
alias /var/lib/mysql/ -> /mysql/,
to /etc/apparmor.d/tunables/alias, and restarted the apparmor service.
Awaiting for further information I'm marking this report as Incomplete again. If you believe this is an actual bug in Ubuntu I encourage you to file a separate report, as it would be almost certainly an issue unrelated with the one this report was originally opened for. Should you follow-up here instead, please set the bug status back to New after replying, and we'll look at it again. Thanks!
Hi,
This seems to be yet a different issue. In order to try to reproduce the problem you faced we need at least to know the following things:
- Which version were you upgrading *from*?
- Was the upgrade part of a release-upgrade to Eoan?
- How exactly did you reconfigure AppArmor to allow
the mysql datadir to be in a location different
from /var/lib/mysql?
Anyway I attempted to reproduce in an upgrade from Disco (mysql-server 5.7.27- 0ubuntu0. 19.04.1) to Eoan (mysql-server 5.7.27-0ubuntu2) and wasn't able to. My alternate datadir was /mysql, and I added the following line:
alias /var/lib/mysql/ -> /mysql/,
to /etc/apparmor. d/tunables/ alias, and restarted the apparmor service.
Awaiting for further information I'm marking this report as Incomplete again. If you believe this is an actual bug in Ubuntu I encourage you to file a separate report, as it would be almost certainly an issue unrelated with the one this report was originally opened for. Should you follow-up here instead, please set the bug status back to New after replying, and we'll look at it again. Thanks!
Thanks!