JBS intermittently responds with 403 when looking up public issues

XMLWordPrintable

    • Type: Bug
    • Resolution: External
    • Priority: P3
    • None
    • Affects Version/s: None
    • Component/s: bots
    • None

      JBS is having intermittent outages atm, causing Skara to fail to lookup issues when running PR CheckRuns. This results in failure to link JBS issues to PRs. It seems JBS is sometimes responding with 403 Forbidden, implying that the user doesn't have permission to view the issue. I think Skara is handling this correctly as there are issues the bot should not be able to access, and in that case, 403 is the expected response and the current action is also correct.

      This is only happening intermittently. There definitely seems to be a correlation with just having refreshed the authentication token.

            Assignee:
            Erik Joelsson
            Reporter:
            Erik Joelsson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: