kubernetes
dnf install of kubeadm kubelet and kubectl 1.32.0 appears to have a stale repo cache
dnf install of kubeadm kubelet and kubectl 1.32.0 appears to have a stale repo cache.
[MIRROR] kubeadm-1.32.0-150500.1.1.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 138 but expected size is: 12311784 [MIRROR] kubectl-1.32.0-150500.1.1.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 138 but expected size is: 11352756 [MIRROR] cri-tools-1.32.0-150500.1.1.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 138 but expected size is: 7466328 [MIRROR] kubeadm-1.32.0-150500.1.1.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 138 but expected size is: 12311784
[FAILED] kubeadm-1.32.0-150500.1.1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/sig cluster-lifecycle release
Content-Length: 138 suggests an error or similar response rather than an RPM. Have a look at the response data @ronmac1978 and see if there's a clue in the response body.
Also, it will be much easier to triage if you include the steps someone should follow to reproduce the problem.
thanks for the response. to attempt the installation we followed https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#kubectl-install-1 Install and Set Up kubectl on Linuxhttps://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#kubectl-install-1 kubernetes.iohttps://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#kubectl-install-1 [icon-128x128.png]https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#kubectl-install-1
the section detailing Install using native package management for res hat based distributions. we have successfully accomplished the steps for 1.28,1.29 and 1.31. additionally we have cleaned the dnd cache to ensure nothing is stale. finally we attempted from anothet system on a separate network. all report the same error. Error details simply state server reported content-length :138 but expected size is 10701856. thanks in advance
On Jan 13, 2025, at 4:54 PM, Tim Bannister @.***> wrote:
/sig cluster-lifecycle release
Content-Length: 138 suggests an error or similar response rather than an RPM. Have a look at the response data @ronmac1978https://github.com/ronmac1978 and see if there's a clue in the response body.
Also, it will be much easier to triage if you include the steps someone should follow to reproduce the problem.
— Reply to this email directly, view it on GitHubhttps://github.com/kubernetes/release/issues/3883, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMVR6R7WTNYF4OI2BMDBDJD2KQ73DAVCNFSM6AAAAABVDTBO2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYGM4TOOBXGY. You are receiving this because you were mentioned.Message ID: @.***>
also this is on a red hat 8 system. red hat 7 works to download and install from repo. thanks again
On Jan 13, 2025, at 4:54 PM, Tim Bannister @.***> wrote:
/sig cluster-lifecycle release
Content-Length: 138 suggests an error or similar response rather than an RPM. Have a look at the response data @ronmac1978https://github.com/ronmac1978 and see if there's a clue in the response body.
Also, it will be much easier to triage if you include the steps someone should follow to reproduce the problem.
— Reply to this email directly, view it on GitHubhttps://github.com/kubernetes/release/issues/3883, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMVR6R7WTNYF4OI2BMDBDJD2KQ73DAVCNFSM6AAAAABVDTBO2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYGM4TOOBXGY. You are receiving this because you were mentioned.Message ID: @.***>
/retitle dnf install of kubeadm kubelet and kubectl 1.32.0 appears to have a stale repo cache
install steps taken from k8s.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.