Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2393

sippy-chat bug with LayeredProduct variant when analyzing test details report

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      i've seen this a couple times now, but it doesn't always happen. Found the problem on this report Just pasting in this link, something doesn't look right with the query params. It's too long. Link was obtained from the main report so should be no shenanigans there.

      If you hit the Ask Sippy button for this report you will see:

      Using tool: get_test_details_report
      Action
      get_test_details_report
      Action Input
      {'query_params': 'Architecture=amd64&FeatureSet=default&Installer=ipi&LayeredProduct=none&Network=ovn&Platform=gcp&Suite=unknown&Topology=ha&Upgrade=micro&baseEndTime=2025-11-05T12%3A00%3A00Z&baseRelease=4.20&baseStartTime=2025-10-06T00%3A00%3A00Z&capability=Other&columnGroupBy=Network%2CPlatform%2CTopology&component=Node+%2F+Kubelet&confidence=95&dbGroupBy=Architecture%2CFeatureSet%2CInstaller%2CLayeredProduct%3Anone%2CNetwork%2CPlatform%2CSuite%2CTopology%2CUpgrade&environment=Architecture%3Aamd64+FeatureSet%3Adefault+Installer%3Aipi+LayeredProduct%3Anone+Network%3Aovn+Platform%3Agcp+Suite%3Aunknown+Topology%3Aha+Upgrade%3Amicro&flakeAsFailure=false&ignoreDisruption=true&ignoreMissing=false&includeMultiReleaseAnalysis=true&includeVariant=Architecture%3Aamd64&includeVariant=Architecture%3Aarm64&includeVariant=Architecture%3Amulti&includeVariant=CGroupMode%3Av2&includeVariant=ContainerRuntime%3Acrun&includeVariant=ContainerRuntime%3Arunc&includeVariant=FeatureSet%3Adefault&includeVariant=FeatureSet%3Atechpreview&includeVariant=Installer%3Ahypershift&includeVariant=Installer%3Aipi&includeVariant=Installer%3Aupi&includeVariant=JobTier%3Ablocking&includeVariant=JobTier%3Ainforming&includeVariant=JobTier%3Astandard&includeVariant=LayeredProduct%3Anone&includeVariant=LayeredProduct%3Avirt&includeVariant=Network%3Aovn&includeVariant=Owner%3Aeng&includeVariant=Owner%3Aservice-delivery&includeVariant=Platform%3Aaws&includeVariant=Platform%3Aazure&includeVariant=Platform%3Agcp&includeVariant=Platform%3Ametal&includeVariant=Platform%3Arosa&includeVariant=Platform%3Avsphere&includeVariant=Topology%3Aexternal&includeVariant=Topology%3Aha&includeVariant=Topology%3Amicroshift&minFail=3&passRateAllTests=0&passRateNewTests=95&pity=5&sampleEndTime=2025-11-05T12%3A00%3A00Z&sampleRelease=4.21&sampleStartTime=2025-10-29T00%3A00%3A00Z&testId=openshift-tests%3A0caf55b5f8fb4676b30d7ec16da1ef92'}
      Observation
      content='{"error": "HTTP 400 - {\\"code\\":400,\\"message\\":\\"invalid variant LayeredProduct:none in variants string Architecture,FeatureSet,Installer,LayeredProduct:none,Network,Platform,Suite,Topology,Upgrade\\"}\\n"}' name='get_test_details_report' tool_call_id='e09ac0de-e009-497d-b2ba-4cf080cc04d1'
      

      and ultimately:

      I encountered an error when trying to retrieve the test details report. The dbGroupBy parameter in the URL contained an invalid variant: LayeredProduct:none. I will attempt to correct this and re-run the analysis.
      

      It stops here and won't proceed with analysis. I believe the AI now tries to re-use the UI Query params to determine the api call to make, so if those are wrong, which may well be the case, it won't work.

              stbenjam Stephen Benjamin
              rhn-engineering-dgoodwin Devan Goodwin
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: