# SOLO-5090

> PodLogsCrdInvalidSoloError — Validation

URL: https://solo.hiero.org/docs/troubleshooting/errors/validation/SOLO-5090/

| | |
|---|---|
| **Code** | `SOLO-5090` |
| **Category** | Validation |
| **Ownership** | Infrastructure |
| **Retryable** | Yes |

## Description

Thrown when the PodLogs CRD YAML fetched for the pinned Grafana Alloy version does not describe the expected `podlogs.monitoring.grafana.com` CustomResourceDefinition. The message names the source URL and the mismatch. The response reached solo but is not the pinned upstream manifest — usually a network intermediary returning an error page or an unrelated file, occasionally an upstream repository move.

## Troubleshooting Steps

1. Re-run the command; a transient upstream response usually clears on retry
1. Confirm that the pinned Grafana Alloy version still ships this CRD at grafana/alloy
1. If the failure keeps recurring, file an issue against grafana/alloy at the pinned version
