Installation / pre-configuration of mysql in server rootfs causes causing problems
Bug #1284208 reported by
Clark Laughlin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro Ubuntu |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
I have been working with devstack on saucy and have been able to install it with no issues.
Once I switched to start working with Linaro hwpack + rootfs builds, I ran into problems related to mysql and not being able to authenticate with the database. I had these problems in the past, but didn't think anything about them until working with it using normal Ubuntu releases, then moving back to Linaro releases.
If I install Saucy, then install mysql, I have no problems.
If I use a server rootfs, I run into the authentication issues.
If I use a nano rootfs and then install mysql, I have no problems.
Is there something being done either to the mysql install or its configuration when building an image using a server rootfs?
| Changed in linaro-ubuntu: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
Revision history for this message
| Fathi Boudra (fboudra) wrote | #1 |
Revision history for this message
| Chase Qi (chase-qi) wrote | #2 |
To post a comment you must log in.
It's a known issue due to a bug in QEMU. When we generate the rootfs, we bootstrap on a non-native host (x86) and use QEMU during the second-stage. Mysql postinst script randomly fails and leave the package not installed properly.
Since it's random, it doesn't happen on all the server rootfs generated. On the broken image, we might be able to reconfigure the package afterward but it isn't acceptable.
The best solution is to fix QEMU but it isn't easy due to the randomness of the bug.
Clark, the latest server image (build #647) should have passed the postinst script properly. You might want to stick to this build.