notifier unable to reach matcher endpoint, returning 404.

[Marais van Zyl]

Description of Problem / Feature Request

Notifier calls the matcher on the wrong endpoint when deployed in a HA scenario.

Because we don't run clair in combo mode, the matcher won't run on the same process as the notifier, so need to use the matcher_addr as defined in the config.

Expected Outcome

Instead of calling the matcher on the relative path, it should call it on the absolute path of the service as specified in the config.

Actual Outcome

logs output:

{
"level": "error",
"component": "notifier/Poller.onTick",
"error": "/matcher/api/v1/internal/update_operation/: unexpected status: 404 Not Found",
"time": "2022-01-10T19:57:06Z",
"message": "client error retrieving latest update operations. backing off until next interval"
}

{
"level": "error",
"UOID": "061d6712-7768-4ce9-9c61-4a95a7e1d827",
"component": "notifier/Processor.process",
"processor_id": 0,
"updater": "RHEL7-openshift-4.3",
"error": "failed to get update diff: /matcher/api/v1/internal/update_diff/: unexpected status: 404 Not Found",
"time": "2022-01-10T19:58:06Z",
"message": "failed to create notifications"
}

Environment

• Clair version/image: 4.3.5
• Clair client name/version:
• Host OS:
• Kernel (e.g. uname -a):
• Kubernetes version (use kubectl version):
• Network/Firewall setup:
  CLAIR_MODE=notifier

[Marais van Zyl]

cancelling as I found the issue with my load balancer config. This is now working as expected.