grml / grml-debootstrap

wrapper around debootstrap
59 stars 27 forks source link

improve error handling 2 #248

Closed adrelanos closed 9 months ago

adrelanos commented 9 months ago

https://github.com/grml/grml-debootstrap/pull/231

adrelanos commented 9 months ago

modprobe loop

modprobe: FATAL: Module loop not found in directory /lib/modules/6.2.0-1015-azure

Seems like an upstream issue as per https://github.com/microsoft/WSL/issues/10450

Previously without strict error handling, the CI simply didn't notice this issue. Solutions:

adrelanos commented 9 months ago
  • A) One easy solution would be to ignore it using "|| true". This requires the least code. I'll do this for now to progress with testing on CI.

Done.

New issue. The following command has a non-zero exit code:

blkid -o value -s TYPE /dev/disk/by-uuid/4f263a0c-b7b6-4998-b066-247fb3310d97

Any idea why that might be?

adrelanos commented 9 months ago

This blkid related bug probably:

Can I ignore it for the purpose of this PR and create a follow-up issue instead? This is what I'll do for now so I can progress with further testing.

adrelanos commented 9 months ago

blkid issue...

Can I ignore it for the purpose of this PR and create a follow-up issue instead? This is what I'll do for now so I can progress with further testing.

Done.

Now, the CI is mostly passing except for the builds of Debian stretch are failing.

+ apt-get update
...
Err:5 http://security.debian.org/ stretch/updates/main amd64 Packages
  404  Not Found
...
W: The repository 'http://security.debian.org/ stretch/updates Release' does not have a Release file.
E: Failed to fetch http://security.debian.org/dists/stretch/updates/main/binary-amd64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

Not sure if this is an intermittent issue because Debian jessie does not have this issue?

Potential solutions:

Quote https://wiki.debian.org/DebianStretch

Security updates have been discontinued as of 2020-07-06.