Not able to see log of PR/release on pipeline visualizer UI

[nagenderRawat]

At the moment pod is going into Completion state the pipeline visualizer UI is showing below error for that piplelinerun -:
the build pods for this build have been garbage collected and the log was not found in the long term storage bucket

Also the processed PR no's list and it's builds( for a repo) are also not getting updated when going inside a particular repo item(in visualizer UI).

At the same time the pod can still be seen at completion state(not garbage collected) and logs are also visible through kubectl get logs cmd but not on UI.
as far as jx get build logs is concern it kind of works but it's also a bit broken, the latest logs are never accurately tagged to the release number.

Workaround tried
I tried diff recent versions of pipeline visualizer and also moved visualizer deployement to jx namespace a well but it also didn't helped.

Logs:
I'am able to see logs on visualizer pod for the pipelinerun link like shown below but no data against it.
time="2020-10-15T21:04:38Z" level=info msg="rendering PipelineRunpr-7vjvl" time="2020-10-15T21:04:53Z" level=info msg="rendering PipelineRunpr-7vjvl" time="2020-10-15T21:05:12Z" level=info msg="rendering PipelineRunpr-7vjvl"

Details that might help in debugging -:
aks cluster
jx cli version-: 3.0.584
jx cluster already updated to latest with jx gitops upgrade
Reran terraform apply on cluster repo create from https://github.com/jx3-gitops-repositories/jx3-azure-terraform (using Use this template)
helmfile release looks like-:
releases:

• chart: jenkins-x/jxboot-helmfile-resources
  version: 1.0.6
  name: jxboot-helmfile-resources
  namespace: jx
  values:
  • versionStream/charts/jenkins-x/jxboot-helmfile-resources/values.yaml.gotmpl
• chart: external-secrets/kubernetes-external-secrets
  version: 5.2.0
  name: kubernetes-external-secrets
  namespace: secret-infra
  values:
  • versionStream/charts/external-secrets/kubernetes-external-secrets/values.yaml.gotmpl
• chart: jx-labs/jenkins-x-crds
  version: 0.0.7
  name: jenkins-x-crds
  namespace: jx
  values:
  • versionStream/charts/jx-labs/jenkins-x-crds/values.yaml
• chart: jx3/jx-preview
  name: jx-preview
  namespace: jx
• chart: stable/nginx-ingress
  version: 1.39.1
  name: nginx-ingress
  namespace: nginx
  values:
  • versionStream/charts/stable/nginx-ingress/values.yaml.gotmpl
• chart: cdf/tekton-pipeline
  version: 0.0.5
  name: tekton-pipeline
  namespace: tekton-pipelines
  values:
  • versionStream/charts/cdf/tekton-pipeline/values.yaml.gotmpl
• chart: jenkins-x/lighthouse
  version: 0.0.851
  name: lighthouse
  namespace: jx
  values:
  • versionStream/charts/jenkins-x/lighthouse/values.yaml.gotmpl
• chart: jenkins-x/nexus
  version: 0.1.35
  name: nexus
  namespace: jx
  values:
  • versionStream/charts/jenkins-x/nexus/values.yaml.gotmpl
• chart: jenkins-x/chartmuseum
  version: 1.1.7
  name: chartmuseum
  namespace: jx
  values:
  • versionStream/charts/jenkins-x/chartmuseum/values.yaml.gotmpl
• chart: banzaicloud-stable/vault-operator
  version: 1.3.0
  name: vault-operator
  namespace: secret-infra
• chart: jx-labs/vault-instance
  version: 0.0.1
  name: vault-instance
  namespace: secret-infra
• chart: jx-labs/pusher-wave
  version: 1.0.0
  name: pusher-wave
  namespace: secret-infra
• chart: oteemocharts/sonarqube
  name: sonarqube
  namespace: sq
• chart: jx3/jx-pipelines-visualizer
  version: 0.0.43
  name: jx-pipelines-visualizer
  namespace: jx-pipelines-visualizer
  values:
  • versionStream/charts/jx3/jx-pipelines-visualizer/values.yaml.gotmpl

@jstrachan @vbehar
Please do let me know if I can help in reproducing this at you side in anyway
Thanks

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten