"Clearsigned file isn't valid" during apt update of Ubuntu 22.04 instance

[LucaGallinari]

Select Topic Area

Bug

Body

Running "apt update" in an action with an Ubuntu 22.04 instance, leads to this error:

E: Failed to fetch https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease' is no longer signed.

[RobinHoutevelts]

We are also seeing this

[johnrhunt]

Yeah, I'm hoping M$ fix this soon.

[JoseSanchez54]

Use runs-on: ubuntu-20.04 instead of runs-on: latest in your .yml

[xalelax]

@JoseSanchez54 This fixed it for me, thanks!

[LucaGallinari]

Use runs-on: ubuntu-20.04 instead of runs-on: latest in your .yml

Should i mark this as an answer until properly addressed by MS?

[jazib194]

Hello! It seems like you are encountering an issue with a "Clearsigned file isn't valid" message during the apt update of your Ubuntu 22.04 instance. This error typically occurs when there is an issue with the signature verification of the repository's metadata.

To resolve this issue, you can try the following steps:

1. Make sure your system's date and time are correctly set.
2. Clear the apt cache by running the command: sudo apt clean.
3. Update the repository key by running: sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com.
4. Try updating the package lists again by running: sudo apt update.

If the issue persists, you may need to check the repository configuration or contact the repository maintainer for further assistance. I hope this helps! Let me know if you need any more assistance for more information click here.

[lyager]

Hit this too

[moffe42]

I think we all are....

[akshhack]

memes

[thuong41]

thinking

[fabien-ors]

Mee too :(

[ruslan-maistrenko]

too

[moffe42]

someone fåågd åb the latest Ubuntu release i guess....

[key-hui-mentem]

me too

[RobinHoutevelts]

🙈 Immediately regretted my comment.
Sorry for starting the mee too train 🚋

[Gewerd-Strauss]

It's the internet, and this was basically inevitable. It's somewhat amusing seeing people slowly arriving here one by one.

[lgmorand]

tchoo tchoo!! climbing on the metoo train

[jigneshgadhavi]

Yes I'm facing same issue with Github action all ubuntu images

[Bojan131]

I also have the same issue. It worked good yesterday.

[Claudius-Appel]

It worked well - or rather, it didn't break stuff - as recent as 3 hours ago. That was when my last action ran successfully P:

[aditya-mangosciences]

I checked this issue just when it was created, and thought its someone like me only to come 5 minutes laters seeing all these comments. 👍
Thanks for confirming its affecting everyone.

[VilleFTW]

This must be addressed quickly. All of our builds are failing

[jypuigbo]

Same here...

[tarasvolosheniuk]

Same problem here. All builds are failing

[Niedman]

Same here...

[jdanielnd]

+1

Using ubuntu-latest resolving to 22.04.4

[Orphail]

+1

[JaLe29]

Playwright https://playwright.dev/ test failing due this issue :-(

name: Playwright tests

on:
  workflow_dispatch:
    inputs:
      username:
        description: 'Start test'
        default: false
        required: true
        type: boolean
  schedule:
    - cron: "0 1 * * *"
jobs:
  tests_e2e:
    name: Run end-to-end tests
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
    - name: Install dependencies
      run: yarn
    - name: Install playwright browsers
      run: npx playwright install --with-deps
    - name: Run tests
      run: yarn  test

[devandrews]

Yes, same for me

[shipplix]

try this: microsoft/playwright#30503 (comment)

[Hirata-Matheus]

Yes, I got it too

[tkpitta]

Same error here, cmon Ubuntu devs (or microsoft package distribution)! We all need you!!

[AleksAlonso]

same here.

[ghzeni]

I'm less worried about how to fix this (specially since changing runs-on: ubuntu-20.04 seems to do the trick) than about why did this happen at all?

[trolleyman]

It's probably because the repo is returning an empty file: https://github.com/orgs/community/discussions/120966#discussioncomment-9211978

No idea why that's the case, but yep that's why.

[ghzeni]

feels great to see sus stuff like this after the xz backdoor 💀

[jepio]

@ghzeni: see this microsoft/linux-package-repositories#130 (comment)

[benner]

At least for me, action went successful.

[Lewenhaupt]

Seems to have been resolved

[jshossen]

Works for me:
runs-on: ubuntu-20.04 instead of runs-on: latest in your .yml

[24icewolf42]

Please don't judge me about security implications, but you can workaround until it is fixed by adding the following options to the sources.list entry: allow-downgrade-to-insecure=yes allow-insecure=yes

$ cat /etc/apt/sources.list.d/microsoft-prod.list
deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg allow-downgrade-to-insecure=yes allow-insecure=yes] https://packages.microsoft.com/ubuntu/22.04/prod jammy main

BTW: It is already fixed, but keep in mind for the next time ;-)

[aditya-mangosciences]

This issue now resolved, We dont need to do anything

[jepio]

Root cause from the PMC team here: microsoft/linux-package-repositories#130 (comment)

[jepio]

Also see this reply from @daviddavis (link)

Apologies for the disruption. It should be resolved now. Our signing service failed to sign the repo files and we'll rolling out a feature to check the repo metadata is signed properly before we publish it. If you all encounter any problems with packages.microsoft.com in the future, please reach out to https://github.com/microsoft/linux-package-repositories/issues.

[petervandenabeele]

My workflows work again without any changes (reran failed job successfully).

[daviddavis]

Apologies for the disruption. It should be resolved now. Our signing service failed to sign the repo files and we'll rolling out a feature to check the repo metadata is signed properly before we publish it. If you all encounter any problems with packages.microsoft.com in the future, please reach out to https://github.com/microsoft/linux-package-repositories/issues.

[jfuruness]

still getting this issue

[daviddavis]

We deployed some fixes this morning that ought to address the issue. Can you try again?

[jfuruness]

looks to be working now, thank you :)

[DevZank]

Me too =(

[jasonzio]

Are you still seeing this behavior? If this is a current issue (2024-04-29 or later) please report it at our issues page here at github.com