Skip to content

opa container throws "status update failed, server replied with HTTP 404 Not Found" but works #798

@maxgruber19

Description

@maxgruber19

Affected Stackable version

25.11.0

Affected OpenPolicyAgent version

1.8.0

Current and expected behavior

After upgrading to 25.11.0 we see some errors in the logs which seem to have no influence on stability of opa but we're curious where they come from and how to avoid them

We already increased log levels as good as we can, maybe you have an idea how to get more details out of opa. currently we don't know which resource is called and returns the 404

  servers:
    cliOverrides: {}
    config:
      logging:
        containers:
          opa:
            loggers:
              console:
                level: DEBUG
              decision:
                level: INFO
              file:
                level: DEBUG
bundle-builder 2026-01-20T08:09:31.963089Z  INFO stackable_opa_bundle_builder: restart done
bundle-builder 2026-01-20T08:09:31.963096Z  INFO stackable_opa_bundle_builder: rebuilding bundle
bundle-builder 2026-01-20T08:09:31.963102Z  INFO stackable_opa_bundle_builder: bundle invalidated, will be rebuilt on next request
bundle-builder 2026-01-20T08:09:33.483366Z  INFO stackable_opa_bundle_builder: building bundle
bundle-builder 2026-01-20T08:09:33.486927Z  INFO stackable_opa_bundle_builder: finished building bundle 
opa {"client_addr":"192.168.3.24:52196","level":"info","msg":"Received request.","req_id":1,"req_method":"GET","req_path":"/","time":"2026-01-20T08:09:34Z","logger":"server"}
opa {"client_addr":"192.168.3.24:52196","level":"info","msg":"Sent response.","req_id":1,"req_method":"GET","req_path":"/","resp_bytes":1433,"resp_duration":0.378743,"resp_status":20
opa {"client_addr":"192.168.3.24:50520","level":"info","msg":"Received request.","req_id":2,"req_method":"GET","req_path":"/","time":"2026-01-20T08:09:44Z","logger":"server"}
opa {"client_addr":"192.168.3.24:50520","level":"info","msg":"Sent response.","req_id":2,"req_method":"GET","req_path":"/","resp_bytes":1433,"resp_duration":0.250666,"resp_status":20
opa {"level":"info","msg":"Bundle loaded and activated successfully.","name":"stackable","plugin":"bundle","time":"2026-01-20T08:09:52Z","logger":"server"}
opa {"level":"error","msg":"status update failed, server replied with HTTP 404 Not Found.","plugin":"status","time":"2026-01-20T08:09:52Z","logger":"server"}
opa {"client_addr":"192.168.3.24:38286","level":"info","msg":"Received request.","req_id":3,"req_method":"GET","req_path":"/","time":"2026-01-20T08:09:54Z","logger":"server"}
opa {"client_addr":"192.168.3.24:38286","level":"info","msg":"Sent response.","req_id":3,"req_method":"GET","req_path":"/","resp_bytes":1433,"resp_duration":0.202943,"resp_status":20

Possible solution

No response

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

None

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions