Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: The redis pod has image pull error when upgrade to 1.83.10-stable [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26783•Fetched 2026-04-30 06:19:57
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
xiaocongjixiaocongji
Participants
xiaocongjixiaocongji
Timeline (top)
labeled ×1

Error Message

Events: Type Reason Age From Message

Normal Scheduled 66s default-scheduler Successfully assigned litellm/litellm-redis-master-0 to ip-172-25-0-58.ec2.internal Warning FailedAttachVolume 66s attachdetach-controller Multi-Attach error for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1" Volume is already exclusively attached to one node and can't be attached to another Normal SuccessfulAttachVolume 54s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1" Normal Pulling 15s (x3 over 53s) kubelet Pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9" Warning Failed 15s (x3 over 53s) kubelet Failed to pull image "docker.io/bitnami/redis:7.2.4-debian-12-r9": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/redis:7.2.4-debian-12-r9": failed to resolve reference "docker.io/bitnami/redis:7.2.4-debian-12-r9": docker.io/bitnami/redis:7.2.4-debian-12-r9: not found Warning Failed 15s (x3 over 53s) kubelet Error: ErrImagePull Normal BackOff 1s (x3 over 53s) kubelet Back-off pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9" Warning Failed 1s (x3 over 53s) kubelet Error: ImagePullBackOff

Code Example

redis:
  enabled: true
  architecture: standalone

---

Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Normal   Scheduled               66s                default-scheduler        Successfully assigned litellm/litellm-redis-master-0 to ip-172-25-0-58.ec2.internal
  Warning  FailedAttachVolume      66s                attachdetach-controller  Multi-Attach error for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1" Volume is already exclusively attached to one node and can't be attached to another
  Normal   SuccessfulAttachVolume  54s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1"
  Normal   Pulling                 15s (x3 over 53s)  kubelet                  Pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9"
  Warning  Failed                  15s (x3 over 53s)  kubelet                  Failed to pull image "docker.io/bitnami/redis:7.2.4-debian-12-r9": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/redis:7.2.4-debian-12-r9": failed to resolve reference "docker.io/bitnami/redis:7.2.4-debian-12-r9": docker.io/bitnami/redis:7.2.4-debian-12-r9: not found
  Warning  Failed                  15s (x3 over 53s)  kubelet                  Error: ErrImagePull
  Normal   BackOff                 1s (x3 over 53s)   kubelet                  Back-off pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9"
  Warning  Failed                  1s (x3 over 53s)   kubelet                  Error: ImagePullBackOff

---
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

I have upgrade the litellm version to 1.83.10-stable and then the redis local pod has image pull error

Here is my simple config

redis:
  enabled: true
  architecture: standalone

And the error I got

Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Normal   Scheduled               66s                default-scheduler        Successfully assigned litellm/litellm-redis-master-0 to ip-172-25-0-58.ec2.internal
  Warning  FailedAttachVolume      66s                attachdetach-controller  Multi-Attach error for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1" Volume is already exclusively attached to one node and can't be attached to another
  Normal   SuccessfulAttachVolume  54s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-53a15474-c25e-40ae-a012-cd9dd17391b1"
  Normal   Pulling                 15s (x3 over 53s)  kubelet                  Pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9"
  Warning  Failed                  15s (x3 over 53s)  kubelet                  Failed to pull image "docker.io/bitnami/redis:7.2.4-debian-12-r9": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/redis:7.2.4-debian-12-r9": failed to resolve reference "docker.io/bitnami/redis:7.2.4-debian-12-r9": docker.io/bitnami/redis:7.2.4-debian-12-r9: not found
  Warning  Failed                  15s (x3 over 53s)  kubelet                  Error: ErrImagePull
  Normal   BackOff                 1s (x3 over 53s)   kubelet                  Back-off pulling image "docker.io/bitnami/redis:7.2.4-debian-12-r9"
  Warning  Failed                  1s (x3 over 53s)   kubelet                  Error: ImagePullBackOff

Steps to Reproduce

Relevant log output

What part of LiteLLM is this about?

No response

What LiteLLM version are you on ?

1.83.10-stable

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The issue is likely due to the Redis image version being unavailable, so updating the Redis image version or using a different version might resolve the issue.

Guidance

  • Check the Bitnami Redis image versions available on Docker Hub to see if the specified version 7.2.4-debian-12-r9 exists.
  • Verify that the LiteLLM configuration is correctly referencing the desired Redis image version.
  • Consider updating the litellm version or the Redis image version to a compatible and available version.
  • If the issue persists, try checking the network connectivity and permissions to pull images from Docker Hub.

Example

No code snippet is provided as the issue seems to be related to image availability rather than code.

Notes

The issue might be specific to the 1.83.10-stable version of LiteLLM, and checking the documentation or release notes for this version might provide more insight into the compatible Redis image versions.

Recommendation

Apply workaround: Use a different available Redis image version, as the specified version seems to be unavailable.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#autograd error#model save/load#optimization#mixed precision#training loop

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: The redis pod has image pull error when upgrade to 1.83.10-stable [1 participants]