Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the chart mysql working with mysql 5.7 version #14827

Closed
gecube opened this issue Feb 10, 2023 · 4 comments · May be fixed by #25947
Closed

Make the chart mysql working with mysql 5.7 version #14827

gecube opened this issue Feb 10, 2023 · 4 comments · May be fixed by #25947
Assignees
@carrodher
Labels
mysql solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@gecube
Copy link
Contributor

gecube commented Feb 10, 2023 •
edited

Name and Version

bitnami/mysql-9.4.8

What steps will reproduce the bug?

  1. Take the chart with all default values
  2. change the image and repo to :
    image:
      registry: docker.io
      repository: bitnami/mysql
      tag: 5.7.41-debian-11-r5
  1. Find that the mysql server is not running.
mysql % kubectl logs dbserver-mysql-0  
mysql 09:19:58.04 
mysql 09:19:58.05 Welcome to the Bitnami mysql container
mysql 09:19:58.05 Subscribe to project updates by watching https://github.com/bitnami/containers
mysql 09:19:58.05 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mysql 09:19:58.06 
mysql 09:19:58.06 INFO  ==> ** Starting MySQL setup **
mysql 09:19:58.08 INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars
mysql 09:19:58.08 INFO  ==> Initializing mysql database
mysql 09:19:58.09 WARN  ==> The mysql configuration file '/opt/bitnami/mysql/conf/my.cnf' is not writable. Configurations based on environment variables will not be applied for this file.
mysql 09:19:58.09 INFO  ==> Using persisted data
mysql 09:19:58.11 INFO  ==> Running mysql_upgrade
mysql 09:19:58.12 INFO  ==> Starting mysql in background

Are you using any custom parameters or values?

yes, I provided the values before.

What is the expected behavior?

The mysql 5.7 is perfectly running as mysql of the latest version. I'd like to emphasise that there are no issues with running on top of 8.0.32-debian-11-r0 image.

The correct run on 8.0.32 looks like

mysql % kubectl logs dbserver-mysql-0 
mysql 08:45:48.52 
mysql 08:45:48.52 Welcome to the Bitnami mysql container
mysql 08:45:48.52 Subscribe to project updates by watching https://github.com/bitnami/containers
mysql 08:45:48.52 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mysql 08:45:48.53 
mysql 08:45:48.53 INFO  ==> ** Starting MySQL setup **
mysql 08:45:48.54 INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars
mysql 08:45:48.55 INFO  ==> Initializing mysql database
mysql 08:45:48.56 WARN  ==> The mysql configuration file '/opt/bitnami/mysql/conf/my.cnf' is not writable. Configurations based on environment variables will not be applied for this file.
mysql 08:45:48.57 INFO  ==> Installing database
mysql 08:45:54.31 INFO  ==> Starting mysql in background
mysql 08:45:56.32 INFO  ==> Configuring authentication
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql 08:45:56.42 INFO  ==> Running mysql_upgrade
mysql 08:45:56.42 INFO  ==> Stopping mysql
mysql 08:45:58.44 INFO  ==> Starting mysql in background
find: '/docker-entrypoint-startdb.d/': No such file or directory
mysql 08:46:06.47 INFO  ==> Stopping mysql
mysql 08:46:09.48 INFO  ==> ** MySQL setup finished! **

mysql 08:46:09.50 INFO  ==> ** Starting MySQL **

What do you see instead?

please get below.

Additional information

I'd like to kindly ask to make the chart compatible with mysql-5.7 as 5.7 is still supported till the October of 2023. We need it to spin up test environments. So I am looking right now for any option to do it.
@gecube gecube added the tech-issues The user has a technical issue about an application label Feb 10, 2023
@bitnami-bot bitnami-bot added this to Triage in Support Feb 10, 2023
@github-actions github-actions bot added the triage Triage is needed label Feb 10, 2023
@carrodher
Copy link
Member

Unfortunately, Bitnami Helm charts are tied to a specific version of the application. If there is more than one branch supported by the application, the one selected to be used in the Helm chart is the latest one according to the upstream releases.

Using a different version can or can't work, but it is not something supported out of the box since the Helm chart (as an isolated package) is built and tested using a specific version (MySQL 8.x in this case).

If you would like to contribute to this Helm chart by fixing any issue to make it compatible with both versions, feel free to create a PR, the Bitnami team will be happy to review it and provide feedback.

@github-actions github-actions bot moved this from Triage to Pending in Support Feb 10, 2023
@gecube
Copy link
Contributor Author

gecube commented Feb 10, 2023

@carrodher Thanks, I will make further investigation.

@bitnami-bot bitnami-bot moved this from Pending to Triage in Support Feb 10, 2023
@carrodher carrodher moved this from Triage to Pending in Support Feb 10, 2023
@github-actions
Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Feb 26, 2023
@github-actions
Copy link

github-actions bot commented Mar 3, 2023

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Mar 3, 2023
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
@bitnami-bot bitnami-bot moved this from Pending to Solved in Support Mar 3, 2023
@github-actions github-actions bot removed this from Solved in Support Mar 7, 2023
@fabiocarneiro fabiocarneiro mentioned this issue May 16, 2024
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carrodher carrodher

Labels
mysql solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[bitnami/mysql] Add a warning on running older versions of MySQL fabiocarneiro/charts
3 participants
@gecube @bitnami-bot @carrodher