Redis fails to install when following tutorial

[atrauzzi]

Steps to reproduce

Following this tutorial.

Observed behavior

Error: {
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please see the details for the specific operation that failed.",
  "target": "/planes/radius/local/resourceGroups/default/providers/Microsoft.Resources/deployments/rad-deploy-835e1848-da2f-408b-9c65-fc59f7b7ca81",
  "details": [
    {
      "code": "ResourceDeploymentFailure",
      "message": "Failed",
      "target": "/planes/radius/local/resourceGroups/default/providers/Applications.Datastores/redisCaches/db",
      "details": [
        {
          "code": "RecipeDownloadFailed",
          "message": "code RecipeLanguageFailure: err failed to fetch repository from the path \"ghcr.io/radius-project/recipes/local-dev/rediscaches:0.43\": Head \"https://ghcr.io/v2/radius-project/recipes/local-dev/rediscaches/manifests/0.43\": dial tcp 140.82.113.34:443: connect: connection refused",
          "details": [
            {
              "code": "RecipeLanguageFailure",
              "message": "failed to fetch repository from the path \"ghcr.io/radius-project/recipes/local-dev/rediscaches:0.43\": Head \"https://ghcr.io/v2/radius-project/recipes/local-dev/rediscaches/manifests/0.43\": dial tcp 140.82.113.34:443: connect: connection refused"
            }
          ]
        }
      ]
    }
  ]
}

Desired behavior

Redis

Workaround

No response

rad Version

0.43.0

Operating system

Running on Fedora 41

Additional context

I'm using podman and kind.

Would you like to support us?

• Yes, I would like to support you

AB#14396

[radius-triage-bot]

👋 @atrauzzi Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👋 @atrauzzi we need more information.

To help us investigate further, we need additional information to reproduce or understand this issue. Please ensure you have steps to reproduce and information about your OS, rad CLI version, and runtime version.

A project maintainer will reply on this issue soon to ask for additional specifics if needed.

For more information on our triage process please visit our triage overview

[sylvainsf]

We were unable to reproduce this issue, it looks like it could be permissions or networking related. If you can get a network trace of your attempt that might reveal the issue.

[atrauzzi]

Whatever it is, I'm working off of a vanilla setup here, so I'm going to wager there's an issue that your tutorial hasn't anticipated.

How would I go about generating the network trace you want?

[atrauzzi]

@sylvainsf -- I can access the URL ghcr.io/radius-project/recipes/local-dev/rediscaches:0.43 in my browser. It redirects to here.

I don't think it's a network issue, but again -- if you can offer something specific for me to run, I'm more than happy! 🙂

[lakshmimsft]

@atrauzzi , can you run the following commands:
kubectl get pods -n radius-system
kubectl exec -it <podname for applications-rp> -n radius-system -- nslookup ghcr.io
kubectl exec -it <podname for applications-rp> -n radius-system -- nc -vz ghcr.io 443
checking if the cluster may be set up with restricting outbound access which can be different from access from the browser.

[atrauzzi]

@lakshmimsft

Here's the output of everything. Your last two commands don't work without a pod, so I put in an arbitrary one from the list.

❯ kubectl get pods -n radius-system

NAME                               READY   STATUS             RESTARTS         AGE
applications-rp-7c7c8b78d9-qftbn   1/1     Running            2 (83m ago)      30h
bicep-de-84d44dddf6-qftpw          1/1     Running            1 (83m ago)      30h
controller-6fd9846bdc-gzg6x        0/1     CrashLoopBackOff   28 (4m55s ago)   30h
dashboard-6fc57b67b5-zbd5g         1/1     Running            17 (83m ago)     30h
database-0                         1/1     Running            1 (83m ago)      30h
dynamic-rp-d668b5c7-nv4sc          1/1     Running            1 (83m ago)      30h
ucp-5779dfc9bf-fqmlv               1/1     Running            2 (82m ago)      30h

❯ kubectl exec -it -n radius-system -- nslookup ghcr.io                           
error: pod, type/name or --filename must be specified

❯ kubectl exec -it bicep-de-84d44dddf6-qftpw  -n radius-system -- nslookup ghcr.io
Server:		10.96.0.10
Address:	10.96.0.10:53

Non-authoritative answer:
Name:	ghcr.io
Address: 140.82.114.34

Non-authoritative answer:

❯ kubectl exec -it -n radius-system -- nc -vz ghcr.io 443
error: pod, type/name or --filename must be specified

❯ kubectl exec -it bicep-de-84d44dddf6-qftpw -n radius-system -- nc -vz ghcr.io 443 
command terminated with exit code 1

Let me know what else to run if you need anything! 🙂

[lakshmimsft]

@atrauzzi Oops! My last two commands had a markdown formatting issue so it hid the pod name. I updated the comment. I wanted the applications-rp pod name in the command.
I'm also curious about some of the pods restarting multiple times, we can run a :
kubectl describe pod controller-6fd9846bdc-gzg6x -n radius-system
and get the logs for it as well:
kubectl logs controller-6fd9846bdc-gzg6x -n radius-system > controllerpodlogs.txt