Add more explicit error logging when fetching detail.

[absoludity]

Signed-off-by: Michael Nelson [email protected]

Description of the change

A user is getting an error in the UX showing "Unable to retrieve chart: sql: no rows in result set" but no corresponding error in the backend. Checking, I found that we don't actually log the error, other than the request log showing the internal error without details:

I0119 19:05:27.529184       1 server.go:314] Requesting chart 'repo/kubeapps%2Fnginx' (latest version) in ns 'default'
I0119 19:05:27.530935       1 server.go:375] Requesting chart 'repo/kubeapps%2Fnginx' (latest version) in ns 'default'
I0119 19:05:27.535286       1 server.go:62] Internal 88.857512ms /kubeappsapis.core.packages.v1alpha1.PackagesService/GetAvailablePackageDetail
I0119 19:05:27.536622       1 server.go:62] Internal 90.361477ms /kubeappsapis.core.packages.v1alpha1.PackagesService/GetAvailablePackageVersions

With this change we'll have details about the actual error in the backend logs.

Benefits

Possible drawbacks

Applicable issues

• fixes #

Additional information

[netlify]

✅ Deploy Preview for kubeapps-dev canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	614f743
🔍 Latest deploy log	https://app.netlify.com/sites/kubeapps-dev/deploys/63c9b5a1f75ca10009309851