Trying to deploy in Kubeapps: 'Could not get information about the resource ConfigMap "" in namespace..."example": resource name may not be empty'

[jlmelladovalle]

Describe the bug
From version 0.50.0, cannot update or fresh deploy through Kubeapps, setting or not custom configmaps.
Is there any configmap not listed in default yaml that must be defined? In previous versions runs perfectly.

To Reproduce
Steps to reproduce the behavior:

1. Deploy/update on Kubeapps.
2. Fill/change yaml definitions as you need, or maintain if you are updating.
3. Press "deploy 0.50.X" button
4. Kubeapps show error:
   "An error occurred: Unable to create the installed package for the package "vector-im/jitsi" using the plugin "helm.packages": rpc error: code = Internal desc = Unable to create helm release "appname" in the namespace "example": Release "appname" failed and has been uninstalled: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource ConfigMap "" in namespace "example": resource name may not be empty"

Expected behavior
It should be deployed with no errors as in previous versions.

Screenshots

Desktop (please complete the following information):

• OS: OSX 13.4
• Browser: Safari

Additional context
Deploying onto k8s 1.25 and 1.26 with same error.

[JonasGoetz01]

Same error:

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource ConfigMap "" in namespace "jitsi": resource name may not be empty

K8s Version 1.26
OS: Ubuntu 22 LTS