```
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
```
Error
```
E:The repository 'https://apt.kubernetes.io kubernetes-xenial
Release' no longer has a Release file., W:Updating from such a
repository can't be done securely, and is therefore disabled by
default., W:See apt-secure(8) manpage for repository creation and
user configuration details., W:An error occurred during the signature
verification. The repository is not updated and the previous index
files will be used. GPG error:
https://packages.gitlab.com/runner/gitlab-runner/ubuntu jammy
InRelease: The following signatures were invalid: EXPKEYSIG
3F01618A51312F3F GitLab B.V. (package repository signing key)
<packages@gitlab.com>
```
I made posting to upgrade team assuming this was some upgrade script with core OS issue
https://bugs.launchpad.net/ubuntu/+s...5/+bug/2076561
But the response I think is to imply one of my channels outside ubuntu is creating the conflict
```
Check the *.sources files in /etc/apt/sources.list.d/ for any that are disabled and re-enable them if you want them back.
$ grep '^Enabled' /etc/apt/sources.list.d/*.sources
Also check any *.list.distUpgrade files in the same directory that you might want to reenable.
root@pandora:/etc/apt/sources.list.d# ls /etc/apt/sources.list.d/
ansible-ubuntu-ansible-jammy.list archive_uri-https_packages_microsoft_com_repos_edge-jammy.list azure-cli.sources helm-stable-debian.list.distUpgrade microsoft-edge-dev.list.distUpgrade runner_gitlab-runner.list.distUpgrade
ansible-ubuntu-ansible-jammy.list.distUpgrade archive_uri-https_packages_microsoft_com_repos_edge-jammy.list.distUpgrade hashicorp.list kubernetes.list plexmediaserver.list
archive_uri-https_apt_releases_hashicorp_com-jammy.list azure-cli.list hashicorp.list.distUpgrade kubernetes.list.distUpgrade plexmediaserver.list.distUpgrade
archive_uri-https_apt_releases_hashicorp_com-jammy.list.distUpgrade azure-cli.list.distUpgrade helm-stable-debian.list microsoft-edge-dev.list runner_gitlab-runner.list
root@pandora:/etc/apt/sources.list.d#
root@pandora:/etc/apt/sources.list.d# grep '^Enabled' /etc/apt/sources.list.d/*.list.distUpgrade
root@pandora:/etc/apt/sources.list.d# grep '^Enabled' /etc/apt/sources.list.d/*.sources
root@pandora:/etc/apt/sources.list.d# cat * |grep -i enable
root@pandora:/etc/apt/sources.list.d#
```
Response I am not sure if it maps to issue. I this is trying to list "Enabled" channels that have been added to the 22.04 distro but the content of these files are just URLs to repos.
Any suggestions on error on upgrade is and next debug steps. My thought is to disable all third party repos for now. Run upgrade then re-enable against new 24.04 channel. But not sure how to do that, and if that maps to proper upgrade workflow.
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
```
Error
```
E:The repository 'https://apt.kubernetes.io kubernetes-xenial
Release' no longer has a Release file., W:Updating from such a
repository can't be done securely, and is therefore disabled by
default., W:See apt-secure(8) manpage for repository creation and
user configuration details., W:An error occurred during the signature
verification. The repository is not updated and the previous index
files will be used. GPG error:
https://packages.gitlab.com/runner/gitlab-runner/ubuntu jammy
InRelease: The following signatures were invalid: EXPKEYSIG
3F01618A51312F3F GitLab B.V. (package repository signing key)
<packages@gitlab.com>
```
I made posting to upgrade team assuming this was some upgrade script with core OS issue
https://bugs.launchpad.net/ubuntu/+s...5/+bug/2076561
But the response I think is to imply one of my channels outside ubuntu is creating the conflict
```
Check the *.sources files in /etc/apt/sources.list.d/ for any that are disabled and re-enable them if you want them back.
$ grep '^Enabled' /etc/apt/sources.list.d/*.sources
Also check any *.list.distUpgrade files in the same directory that you might want to reenable.
root@pandora:/etc/apt/sources.list.d# ls /etc/apt/sources.list.d/
ansible-ubuntu-ansible-jammy.list archive_uri-https_packages_microsoft_com_repos_edge-jammy.list azure-cli.sources helm-stable-debian.list.distUpgrade microsoft-edge-dev.list.distUpgrade runner_gitlab-runner.list.distUpgrade
ansible-ubuntu-ansible-jammy.list.distUpgrade archive_uri-https_packages_microsoft_com_repos_edge-jammy.list.distUpgrade hashicorp.list kubernetes.list plexmediaserver.list
archive_uri-https_apt_releases_hashicorp_com-jammy.list azure-cli.list hashicorp.list.distUpgrade kubernetes.list.distUpgrade plexmediaserver.list.distUpgrade
archive_uri-https_apt_releases_hashicorp_com-jammy.list.distUpgrade azure-cli.list.distUpgrade helm-stable-debian.list microsoft-edge-dev.list runner_gitlab-runner.list
root@pandora:/etc/apt/sources.list.d#
root@pandora:/etc/apt/sources.list.d# grep '^Enabled' /etc/apt/sources.list.d/*.list.distUpgrade
root@pandora:/etc/apt/sources.list.d# grep '^Enabled' /etc/apt/sources.list.d/*.sources
root@pandora:/etc/apt/sources.list.d# cat * |grep -i enable
root@pandora:/etc/apt/sources.list.d#
```
Response I am not sure if it maps to issue. I this is trying to list "Enabled" channels that have been added to the 22.04 distro but the content of these files are just URLs to repos.
Any suggestions on error on upgrade is and next debug steps. My thought is to disable all third party repos for now. Run upgrade then re-enable against new 24.04 channel. But not sure how to do that, and if that maps to proper upgrade workflow.