[Mediawiki] Pod in Crashlookbackoff

[stanbog]

Name and Version

bitnami/mediawiki 20.2.7

What architecture are you using?

amd64

What steps will reproduce the bug?

While trying to install the mediawiki helm chart via ArgoCD on Openshift, the mediawiki pod crashes continuously with this the following log:

[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> 
[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> [1mWelcome to the Bitnami mediawiki container[0m
[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> Subscribe to project updates by watching [1mhttps://github.com/bitnami/containers[0m
[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> Submit issues and feature requests at [1mhttps://github.com/bitnami/containers/issues[0m
[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit [1mhttps://bitnami.com/enterprise[0m
[38;5;6mmediawiki [38;5;5m10:16:13.65 [0m[38;5;2mINFO [0m ==> 
[38;5;6mmediawiki [38;5;5m10:16:13.66 [0m[38;5;2mINFO [0m ==> ** Starting MediaWiki setup **
[38;5;6mmediawiki [38;5;5m10:16:13.66 [0m[38;5;5mDEBUG[0m ==> Validating settings in APACHE_* environment variables
[38;5;6mmediawiki [38;5;5m10:16:13.67 [0m[38;5;5mDEBUG[0m ==> Copying files from /opt/bitnami/apache/conf.default to /opt/bitnami/apache/conf
realpath: /bitnami/apache/conf: No such file or directory
[38;5;6mmediawiki [38;5;5m10:16:13.68 [0m[38;5;2mINFO [0m ==> Configuring the HTTP port
[38;5;6mmediawiki [38;5;5m10:16:13.69 [0m[38;5;5mDEBUG[0m ==> Configuring port 8080 on file /opt/bitnami/apache/conf/httpd.conf
[38;5;6mmediawiki [38;5;5m10:16:13.69 [0m[38;5;5mDEBUG[0m ==> Configuring port 8080 on file /opt/bitnami/apache/conf/bitnami/bitnami.conf
[38;5;6mmediawiki [38;5;5m10:16:13.69 [0m[38;5;5mDEBUG[0m ==> Configuring port 8080 on file /opt/bitnami/apache/conf/vhosts/00_status-vhost.conf
[38;5;6mmediawiki [38;5;5m10:16:13.69 [0m[38;5;2mINFO [0m ==> Configuring the HTTPS port
[38;5;6mmediawiki [38;5;5m10:16:13.69 [0m[38;5;5mDEBUG[0m ==> Configuring port 8443 on file /opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf
[38;5;6mmediawiki [38;5;5m10:16:13.70 [0m[38;5;2mINFO [0m ==> Configuring Apache ServerTokens directive
[38;5;6mmediawiki [38;5;5m10:16:13.70 [0m[38;5;5mDEBUG[0m ==> Configuring ServerTokens Prod on file /opt/bitnami/apache/conf/httpd.conf
[38;5;6mmediawiki [38;5;5m10:16:13.71 [0m[38;5;2mINFO [0m ==> Configuring PHP options
[38;5;6mmediawiki [38;5;5m10:16:13.71 [0m[38;5;2mINFO [0m ==> Setting PHP expose_php option
[38;5;6mmediawiki [38;5;5m10:16:13.74 [0m[38;5;2mINFO [0m ==> Setting PHP output_buffering option
[38;5;6mmediawiki [38;5;5m10:16:13.75 [0m[38;5;2mINFO [0m ==> Validating settings in MYSQL_CLIENT_* env vars
[38;5;6mmediawiki [38;5;5m10:16:13.77 [0m[38;5;5mDEBUG[0m ==> Validating settings in MEDIAWIKI_* environment variables...
[38;5;6mmediawiki [38;5;5m10:16:13.77 [0m[38;5;3mWARN [0m ==> You set the environment variable ALLOW_EMPTY_PASSWORD=true. For safety reasons, do not use this flag in a production environment.
[38;5;6mmediawiki [38;5;5m10:16:13.96 [0m[38;5;2mINFO [0m ==> Restoring persisted MediaWiki installation
[38;5;6mmediawiki [38;5;5m10:16:13.99 [0m[38;5;2mINFO [0m ==> Trying to connect to the database server
[38;5;6mmediawiki [38;5;5m10:16:13.99 [0m[38;5;5mDEBUG[0m ==> Getting $wgDBserver from MediaWiki configuration
[38;5;6mmediawiki [38;5;5m10:16:14.00 [0m[38;5;5mDEBUG[0m ==> ^\s*(//\s*)?\$wgDBserver\s*=([^;]+);
grep: /opt/bitnami/mediawiki/LocalSettings.php: No such file or directory

We're using target version 20.2.7.

Most of the parameters are taken from the default values.yaml file.

The MariaDB pod doesn't have this issue, it starts fine.

Are you using any custom parameters or values?

podSecurityContext: false
containerSecurityContext: false
global.compatibility.openshift.adaptSecurityContext: true
mediawikiHost: xxx
mediawikiUser: xxx
mediawikiPassword: xxx
mariadb.auth.rootPassword: xxx
mariadb.auth.password: xxx
image.debug: true
resourcesPreset: medium
mediawikiEmail: [email protected]
mediawikiName: MediaWiki POC
allowEmptyPassword: true
replicaCount: 1
ingress.enabled: true
ingress.hostname: xxx
ingress.tls: true

What is the expected behavior?

For the pod to be Ready

What do you see instead?

Pod is crashing

[carrodher]

The issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a specific scenario that is not easy to reproduce on our side. Our internal testing is working fine in the different platforms we use for testing: OpenShift, AKS, EKS, TKG, etc.

If you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[github-actions[bot]]

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[bot]]

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.