If mysql is configured to use the ndb engine a karmic upgrade should keep mysql-dfsg-5.0 and remove the mysql-server package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Karmic |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
During the Karmic release cycle, MySQL has been updated from 5.0 to 5.1 in main. That means that the mysql-server binary package is now depending on mysql-server-5.1 instead of mysql-server-5.0. update-manager already supports upgrading mysql-server from 5.0 to 5.1 - see bug 413789.
However there is one use case where the upgrade should not be done. If mysql-server is setup as part of a MySQL cluster (ndb engine), the system should not be upgraded to 5.1. Instead the mysql-server binary package should be removed (as it would pull 5.1 in) and 5.0 should be upgraded instead (which is in universe in karmic).
There is already a check in mysql-server-
# Abort if an NDB cluster is in use.
if egrep -qi -r '^[^#]*
db_fset mysql-server/
db_input high mysql-server/
db_go
db_stop
exit 1
fi
Removing mysql-server should be done before an upgrade is performed.
Changed in update-manager (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in update-manager (Ubuntu Karmic): | |
assignee: | nobody → Michael Vogt (mvo) |
Changed in update-manager (Ubuntu Karmic): | |
milestone: | none → ubuntu-9.10 |
Here is an example configuration file for the sql and data nodes:
# Options for mysqld process: ng=192. 168.0.10 # location of management server
[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstri
# Options for ndbd process: ng=192. 168.0.10 # location of management server
[mysql_cluster]
ndb-connectstri