So, during the upgrade, mysql does get 'stuck' on:
Setting up mysql-client-5.1 (5.1.54-1ubuntu4) ...
Setting up mysql-server-5.1 (5.1.54-1ubuntu4) ...
Installing new version of config file /etc/init/mysql.conf ...
The upstart job keeps running the pre-start script every 30 seconds, but no change to the profile makes this go away. In fact, the profile should be good enough as is:
$ sudo apparmor_parser -p /etc/apparmor.d/usr.sbin.mysqld |grep network
network inet stream,
network inet6 stream,
network inet dgram,
network inet6 dgram,
network tcp,
This seems like a maverick kernel vs natty apparmor userspace issue.
So, during the upgrade, mysql does get 'stuck' on: mysql.conf ...
Setting up mysql-client-5.1 (5.1.54-1ubuntu4) ...
Setting up mysql-server-5.1 (5.1.54-1ubuntu4) ...
Installing new version of config file /etc/init/
The upstart job keeps running the pre-start script every 30 seconds, but no change to the profile makes this go away. In fact, the profile should be good enough as is: d/usr.sbin. mysqld |grep network
$ sudo apparmor_parser -p /etc/apparmor.
network inet stream,
network inet6 stream,
network inet dgram,
network inet6 dgram,
network tcp,
This seems like a maverick kernel vs natty apparmor userspace issue.