Closed syjung6967 closed 2 years ago
Hi
Please, note the Bitnami team is not actively monitoring GitHub Issues for this chart. This issue will stay open for 20 days to allow the community to contribute, after 15 days without activity the issue will be marked as stale being closed after 5 days. If you would like to contribute to this chart by fixing a bug or adding a new feature feel free to create a PR, the Bitnami team will be happy to review it and provide feedback.
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.
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.
Which chart: Charts that depend on mariadb such as bitnami/mediawiki (13.0.1)
Describe the bug
I am trying to install both mediawiki and mariadb using bitnami/mediawiki chart on EC2 Ubuntu 20.04.3 LTS (ami-0454bb2fefc7de534) atop c5a.2xlarge instance. At first, I installed bitnami/mediawiki only adding namespace.
Then I got following error.
With or without the namespace, the above error rarely does not occur but unfortunately I do not know how to reproduce it. Also, even though mariadb becomes ready luckily, mediawiki service remains pending state. I executed the given commands in the error message and tried other older version charts but the problem still remains. (kubectl is aliased in .bashrc as
alias kubectl='minikube kubectl --'
command)Furthermore, I checked other charts installing mariadb as dependency. Wordpress and Joomla offer their services with no error but owncloud remains pending state due to the above mariadb error.
To Reproduce
Docker, minikube, and helm are installed by following each own manual.
Expected behavior
Run mariadb with no error so that main service like mediawiki works well.
Version info