rancher: Apps Catalog Repositories stuck "In Progress" (Centos 7)

Rancher Server Setup

  • Rancher version: v2.7.1
  • docker 23.0.1
  • upgraded kernel from 3.10 to 5.4 (kernel-lt longterm with headers and devel)
  • Installation option (Docker install/Helm Chart): docker run -d --name rancher --restart=unless-stopped -p 80:80 -p 443:443 -v /etc/pki/ca-trust/extracted/pem/cacerts.pem:/etc/rancher/ssl/cert.pem -v /etc/pki/ca-trust/extracted/pem/key.pem:/etc/rancher/ssl/key.pem --privileged rancher/rancher:v2.7.1 --no-cacerts

Information about the Cluster

  • (not relevant?) Kubernetes version: k3s 1.25.6

User Information

  • What is the role of the user logged in? Admin

Describe the bug fresh install on a fresh (Centos 7) server, Apps Catalog Repositories don’t download - stuck “In Progress” rancher-repo-pull-in-progress

To Reproduce install 23.0.1 docker and start 2.7.1 rancher on Centos 7

Result Apps Catalog Repositories don’t download - stuck “In Progress”

Expected Result Apps Catalog Repositories are “Ready”

** Troubleshooting done** From command-line on the server, bash-4.2$ git clone https://git.rancher.io/partner-charts pulls the repo, and curl https://prometheus-community.github.io/helm-charts/ brings back the HTML but in Rancher it isn’t working

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 4
  • Comments: 22

Most upvoted comments

having the exact same behaviour.

Workaround: upgrade to Rancher v2.7.2-rc7

I’ve just upgraded to rancher 2.7.9 and this problem comes back…

#38701

@dgadelha is this resolved in Rancher v2.7.2 with K3S 1.25 and above? I’d like to upgrade to 1.25.x at some point but am a bit gun shy

Yes, we’re on 2.7.2 and it’s working fine on 1.25 clusters.

image

@mike12806 , thanks for the information. I managed to downgrade my K3S cluster to 1.24.10 by following the guide this url: https://thehotelhero.com/upgrading-downgrading-k3s . The Apps catalog repositories are not longer stuck after I downgraded my cluster.

Had the same behavior, had to downgrade back to K3S 1.24.10 to get it working again 👎

@mike12806 , how did you downgrade the k3s version?

@mike12806 thanks, that fixed, I just had to update 1 of the master nodes and it unstuck it. everything else is still on the latest.