Yes, checked with 5.5.30-23.7.4-405.precise version.
To be exact: if you have my.cnf with a variable that prevents XtraDB Cluster from start, like bind_address = 127.0.0.1, the install fails on final configuration stage, so the package status is:
iF percona-xtradb-cluster-server-5.5 5.5.30-23.7.4-405.precise Percona Server database server binaries
But that's a normal Ubuntu and Debian style - the service must be successfully started in order to confirm the package install has been completed. So I don't think this is a bug. All you have to do to finalize the install is to fix the my.cnf and do:
dpkg --configure percona-xtradb-cluster-server-5.5
I can't confirm the socket variable problem though, when I set it to the same as default, that is:
socket = /var/run/mysqld/mysqld.sock
the init script works well, as well as installation process.
@Raghavendra,
Yes, checked with 5.5.30- 23.7.4- 405.precise version. xtradb- cluster- server- 5.5 5.5.30- 23.7.4- 405.precise Percona Server database server binaries
To be exact: if you have my.cnf with a variable that prevents XtraDB Cluster from start, like bind_address = 127.0.0.1, the install fails on final configuration stage, so the package status is:
iF percona-
But that's a normal Ubuntu and Debian style - the service must be successfully started in order to confirm the package install has been completed. So I don't think this is a bug. All you have to do to finalize the install is to fix the my.cnf and do: xtradb- cluster- server- 5.5
dpkg --configure percona-
I can't confirm the socket variable problem though, when I set it to the same as default, that is: mysqld/ mysqld. sock
socket = /var/run/
the init script works well, as well as installation process.