An error occurred while fetching the catalog: Unable to get the available package detail for the package "bitnami/mysql" using the plugin "helm.packages": internal: Unable to retrieve chart files: sql: no rows in result set.

[fea359]

Name and Version

bitnami/mysql

What architecture are you using?

amd64

What steps will reproduce the bug?

When I searched for mysql, tomcat, and redis using kubeapps, I was able to find these applications, but when I deployed them, it prompted: "An error occurred while fetching the catalog: Unable to get the available package detail for the package "bitnami/mysql" using the plugin "helm.packages": internal: Unable to retrieve chart files: sql: no rows in result set."
But helm search was able to search and install them.
I found the mysql record in the database files, and indeed did not find the record of 12.1.0, but I found the record of 12.0.0, and then I changed 12.0.0 to 12.1.0 and it succeeded. There are many similar situations, such as redis-cluster.
The root cause is that the records in the files table in PostgreSQL have not been updated in a timely manner.

Are you using any custom parameters or values?

no

What is the expected behavior?

No response

What do you see instead?

Additional information

No response

[carrodher]

Hi, 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 particular scenario that is not easy to reproduce on our side. Probably the best place to look for support is at https://github.com/vmware-tanzu/kubeapps.

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.

[fea359]

Crstal clean,Thanks.
This problem is easy to reproduce. For any installed or newly installed kubeapps, the same error will appear when searching for mysql, because after Syncing Package Repositories is completed, there is no latest sql record in postgres.
The problem is that the kubeapps scheduled task apprepo-kubeapps-sync cannot pull the latest data when pulling data from https://charts.bitnami.com/bitnami and storing it in postgresql.