Uploaded image for project: 'Red Hat Developer Hub Bugs'
  1. Red Hat Developer Hub Bugs
  2. RHDHBUGS-2597

Error accessing a previous conversation in Lightspeed chat history

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 1.8.2
    • Lightspeed
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      The following error appears if the user wants to reuse a previous chat in Lightspeed:

      This error only appears when the chat was created previously and the RHDH pod was restarted. If the chat was created in the same pod instance, then it is possible to update it and continue the conversation.

      Attached the LCS container pod where it is possible to get the authorization errors to update the chat.backstage-developer-hub-5b664d69c9-k8cz8-lightspeed-core.log

      Prerequisites (if any, like setup, operators/versions):

      OpenShift 4.20

      Red Hat Developer Hub 1.8.2 (installed by the Operator)

      Steps to Reproduce

      1. Create a new chat history with any message.
      2. Move to another chat (or place in Red Hat Developer Hub) ui.
      3. Come back to Lightspeed and click in the previous chat open. 
      4. Continue the conversation.
      5. Restart the RHDH deployment, e.g: `oc rollout restart deployment/backstage-developer-hub`
      6. Come back to Lightspeed and click in the previous chat created.
      7. Continue the conversation
      8. Fails with the error reported.

      Actual results:

      Unable to continue a chat if there is a pod restart.

      Expected results:

      Continue any chat whatever was created and independetly of pod life cycle.

      Reproducibility (Always/Intermittent/Only Once): Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

              Unassigned Unassigned
              rmarting@redhat.com Roman Martin Gil
              RHDH AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: