Sandbox gets in a unknown state if creation fails

[Daniël van Eeden]

I installed MySQL Sandbox 3.0.30 and downloaded MySQL 5.6.10.

Then I tried to create a sandbox:
make_sandbox Downloads/mysql-5.6.10-linux-glibc2.5-x86_64.tar.gz
...
error while creating grant tables
Installing MySQL system tables.../home/dveeden/Downloads/5.6.10/bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

The result is a sandbox in a unknown state.

Then I installed libaio1 and tried again:
make_sandbox Downloads/mysql-5.6.10-linux-glibc2.5-x86_64.tar.gz
...
/home/dveeden/sandboxes/msb_5_6_10 already exists.
'--force' option not specified.
Installation halted

After removing the sandbox and retrying again it worked.

Maybe this could be solved by:
- Giving a warning before a 5.5+ sandbox is created on a system without libaio1
- Removing the sandbox if the creation failed. (rollback to known position)

[Giuseppe Maxia (giuseppe-maxia)]

A warning on dependencies is not easy to implement, although it should not be too hard.

About removing the sandbox, I am not sure. The failure happens when the sandbox start, and it could happen also at a later stage, not only with the installation.

Currently, there are a few options:

1) After installing libaio, repeating the installation with -- --force should fix the problem.

2) instead of reinstalling with --force, you can remove the sandbox:

$ sbtool -o delete -s ~/sandboxes/msb_5_6_10
$ make_sandbox ...