Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to install dotnet core 3.1.11 on SLES 12 SP5 #5856

Closed
rtssrl opened this issue Jan 15, 2021 · 15 comments
Closed

Fail to install dotnet core 3.1.11 on SLES 12 SP5 #5856

rtssrl opened this issue Jan 15, 2021 · 15 comments
Assignees
Labels
area-setup Issues related to installing .NET Core

Comments

@rtssrl
Copy link

rtssrl commented Jan 15, 2021

Following instructions at https://docs.microsoft.com/en-us/dotnet/core/install/linux-sles:

zypper in aspnetcore-runtime-3.1

got:

Installation of dotnet-runtime-3.1-3.1.11-1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.11/Microsoft.VisualBasic.Core.dll;6001d5be: cpio: read failed - No such file or directory
error: dotnet-runtime-3.1-3.1.11-1.x86_64: install failed

Version 3.1.10 is OK

@mairaw mairaw added the area-setup Issues related to installing .NET Core label Jan 15, 2021
@mairaw
Copy link
Contributor

mairaw commented Jan 15, 2021

@leecow @dagood can you help here?

@dagood
Copy link
Member

dagood commented Jan 15, 2021

@rbhanda maybe this is related to other 3.1.11 packages.microsoft.com issues? #5838
/cc @NikolaMilosavljevic

@rbhanda
Copy link
Contributor

rbhanda commented Jan 15, 2021

I was able to install .NET 5.0.102 SDK on a SLES linux machine. I wonder if this is related to folks hitting a different mirror and that is why I am not able to repro this.

@rtssrl
Copy link
Author

rtssrl commented Jan 18, 2021

Now, I noticed that http://packages.microsoft.com/sles/12/prod/dotnet-runtime-3.1.11-x64.rpm is tiny compared to others

repository_screenshot

@rbhanda
Copy link
Contributor

rbhanda commented Jan 18, 2021

Thanks for pointing this out @rtssrl
I have re-uploaded this file and I can download the file with 28.7 MB size

@rtssrl
Copy link
Author

rtssrl commented Jan 19, 2021

OK, Thanks!
Now error seems to be with aspnetcore-runtime-3.1.11-x64.rpm

error_aspnetcore_runtime

I've tried to removed packages, cleared zypper cache and re-run zypper in aspnetcore-runtime-3.1

aspnetcore-runtime-3.1.11-x64.rpm looks a bit smaller than aspnetcore-runtime-3.1.10-x64.rpm

@rbhanda
Copy link
Contributor

rbhanda commented Jan 19, 2021

hi @rtssrl thanks a lot for reporting this. I am trying to get to the root cause of these files getting corrupted. I will keep this thread updated with the progress.

@rbhanda
Copy link
Contributor

rbhanda commented Jan 19, 2021

The aspnetcore-runtime-3.1.11-x64.rpm corruption issue should be resolved now.

@beanotj
Copy link

beanotj commented Jan 19, 2021

Don't know if this is related, but I'm having a similar issue with dotnet-sdk-3.1-3.1.405-1.x86_64:
image

Same file size issue:
image

@rbhanda
Copy link
Contributor

rbhanda commented Jan 19, 2021

Thanks a lot for reporting @beanotj . I have updated the file and it should get reflected on packages,microsoft.com in some time (~20 mins)

@beanotj
Copy link

beanotj commented Jan 19, 2021

@rbhanda: Everything looks good, thanks!

@rtssrl
Copy link
Author

rtssrl commented Jan 20, 2021

Hi @rbhanda, now zypper in aspnetcore-runtime-3.1 is OK, thanks!

@Chardrazle
Copy link

We're still seeing issues trying to acquire a non-corrupted version of: dotnet-sdk-3.1.405-x64.rpm
The corrupted version appears to have spread around the Azure nodes.
Sometimes we've got lucky and acquired the correct package, but most times not. Depends on which mirror we ultimately hit, I guess.

For example:
wget http://csd-apt-weu-d-4.westeurope.cloudapp.azure.com/yumrepos/microsoft-rhel7.3-prod/dotnet-sdk-3.1.405-x64.rpm -O- | md5sum

The corrupted version returns the checksum: 5eb9c4854342778b93d5ef55e83d265a
This file is 68MB and fails to install.

The correct version returns the checksum: 3d4b099cbc73b62e673c9c84a234f0a2

@Chardrazle
Copy link

To follow up, we've not had any occurrences of the corrupt version for at least a week now. So it looks like the correct one has propagated.

@danmoseley
Copy link
Member

Ok good. Closing. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-setup Issues related to installing .NET Core
Projects
None yet
Development

No branches or pull requests

8 participants