Nil response

[kirk-patton]

We are using OPA in a k8s environment.

• OPA version: 0.56.0
• Response is nil
• flags
• "run",
  "--server",
  "--config-file=/config/config.yaml",
  "--log-level=info",
  "--log-format=json",
  "--authentication=token",
  "--authorization=basic",
  "/authz/authz.rego",
  "/authz/bearer.rego",
  "--ignore=.*",
  "--addr=http://127.0.0.1:8181"

Steps To Reproduce

The error happen over time. No discernible pattern other than a restart of OPA fixes it.

When the "nil" response starts happening it is reproducible until OPA is restarted.
Is there a way to gather more information when this happens?

[ashutosh-narkar]

@kirk-patton closing this for now. Feel free to re-open with more details about the issue and steps to reproduce it. Thanks!

[anderseknert]

@ashutosh-narkar the details were hidden as they had been provided as part of the comment included in the template. I edited the issue to unhide that.

[ashutosh-narkar]

@kirk-patton I would recommend using the latest version of OPA and try to repro with that. Also it would help if you could share the policy, input etc. There were some issues around OPA returning a "nil" response in an older version which we fixed. Not sure if you're seeing the same issue but using the latest OPA version would help to figure that out.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.