release icon indicating copy to clipboard operation
release copied to clipboard

Error while installing kubernetes "kubernetes-xenial Release' does not have a Release file."

Open awsdevopz opened this issue 1 year ago • 3 comments

What happened:

While installing Kubernetes on ubuntu, I am encountering the below error

apt-get update Hit:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 https://download.docker.com/linux/ubuntu jammy InRelease Hit:7 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:5 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.28/deb InRelease Ign:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease Err:8 https://packages.cloud.google.com/apt kubernetes-xenial Release 404 Not Found [IP: 172.253.62.139 443] Reading package lists... Done E: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

Even after following the below document, I am unable to install https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/#how-to-migrate-deb

Please look into it on priority

What you expected to happen:

Clean install of kubernetes

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

Internal

  • Cloud provider or hardware configuration: AWS

  • OS (e.g: cat /etc/os-release): PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

  • Kernel (e.g. uname -a): Linux 6.5.0-1014-aws #14~22.04.1-Ubuntu SMP Thu Feb 15 15:27:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  • Others:

awsdevopz avatar Apr 08 '24 14:04 awsdevopz

You need to completely remove apt.kubernetes.io repository from your system. See #3485 for more details.

xmudrii avatar Apr 08 '24 14:04 xmudrii

root@ip-:/# echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /

root@ip-:/# curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.28/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

root@ip-:/# apt update Hit:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:5 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:6 https://download.docker.com/linux/ubuntu jammy InRelease Ign:4 https://packages.cloud.google.com/apt kubernetes-xenial InRelease Hit:7 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.28/deb InRelease Err:8 https://packages.cloud.google.com/apt kubernetes-xenial Release 404 Not Found [IP: 172.253.122.100 443] Reading package lists... Done E: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

I am unable to figure out from where apt.kubernetes.io is being picked up. Please help me with it

awsdevopz avatar Apr 08 '24 14:04 awsdevopz

You still have apt.kubernetes.io and/or packages.cloud.google.com/apt kubernetes-xenial enabled on your system. It might not be necessary in /etc/apt/sources.list.d/kubernetes.list, it might be in some other location. We can't help you much there, but I recommend inspecting what repositories you have enabled in /etc/apt/sources.list and /etc/apt/sources.list.d

xmudrii avatar Apr 08 '24 14:04 xmudrii

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

k8s-triage-robot avatar Jul 07 '24 15:07 k8s-triage-robot

If the issue is still present, please let us know or create a new issue. /close

xmudrii avatar Jul 22 '24 17:07 xmudrii

@xmudrii: Closing this issue.

In response to this:

If the issue is still present, please let us know or create a new issue. /close

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.

k8s-ci-robot avatar Jul 22 '24 17:07 k8s-ci-robot