Skip to content
This repository has been archived by the owner on Jul 24, 2019. It is now read-only.

bug: mariadb chart readiness probe fails with kolla/*-binary-mariadb image #253

Open
wilreichert opened this issue Mar 7, 2017 · 4 comments

Comments

@wilreichert
Copy link
Contributor

The mariadb chart readiness probe uses pymysql which is not installed in the kolla mariadb images. End result is the database starts fine but the container is never marked as read due to the probe failure.

@intlabs
Copy link
Contributor

intlabs commented Mar 7, 2017

@wilreichert good catch!

@alanmeadows, would it make sense to explore using a more portable mysql binary client and shell based readiness check?

@alanmeadows
Copy link
Contributor

alanmeadows commented Mar 7, 2017

The check that is currently python based is extremely simplistic, we can easily replace it with a simpler, less dependent check.

We will need to be able to:

  • Loop forever until success
  • Do error code checking/casing

This should be possible in shell with the mysql client.

@ap2516
Copy link

ap2516 commented Mar 7, 2017

I can work on this

@andrecolin
Copy link

The peer finder python script is also affected. Taking a look at it now

@v1k0d3n v1k0d3n changed the title mariadb chart readiness probe fails with kolla/*-binary-mariadb image bug: mariadb chart readiness probe fails with kolla/*-binary-mariadb image Mar 8, 2017
@v1k0d3n v1k0d3n added the bug label Mar 8, 2017
@v1k0d3n v1k0d3n added this to the 0.3.0 milestone Mar 8, 2017
@mcnanci mcnanci moved this from TODO to In Progress in openstack-helm 0.3.0 Milestones Mar 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging a pull request may close this issue.

6 participants