Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    megamaced
    @megamaced
    i did delete the packages from the channel, then I deleted the packages from "packages not in any channel"
    then I did the spacewalk-repo-sync which downloaded them again
    it actually downloaded them, not linked them from elsewhere
    but did not resolve the issue
    Julio González Gil
    @juliogonzalez
    mmmmm, really strange, it could be a bug, then
    megamaced
    @megamaced
    If I manually download the x11-video-nvidiaG04-390.129-lp151.7.1.x86_64.rpm from nVidia and run sha256sum I get bdb00a07f2953a7285023a13b479e49ec6e919635a8f7f9e50ec31cfb492d4f2. If I manually download x11-video-nvidiaG04-390.129-lp151.7.1.x86_64.rpm from Uyuni via the Web UI in a browser I also get bdb00a07f2953a7285023a13b479e49ec6e919635a8f7f9e50ec31cfb492d4f2
    Julio González Gil
    @juliogonzalez
    ah, sorry, x11-video
    megamaced
    @megamaced
    yep
    /var/spacewalk/packages/1 # find ./ -type f -name "x11-video-nvidiaG04"
    ./c0c/x11-video-nvidiaG04/390.129-lp150.7.1/x86_64/c0c8f08792f0779fd3f970690e635de9076b9a9fc1f88c98206b0c56ee328b4e/x11-video-nvidiaG04-390.129-lp150.7.1.x86_64.rpm
    ./339/x11-video-nvidiaG04/390.116-lp150.10.1/x86_64/3390d558ef829b32936c8a95ca068e81d427a50d0e3a78bee445990c088092ff/x11-video-nvidiaG04-390.116-lp150.10.1.x86_64.rpm
    ./e5e/x11-video-nvidiaG04/390.116-lp150.7.1/x86_64/e5e6968c2b44ba7b4ea815edd7a4d9b2d09eb55db2d6d7358d33071e11fe492d/x11-video-nvidiaG04-390.116-lp150.7.1.x86_64.rpm
    ./bdb/x11-video-nvidiaG04/390.129-lp151.7.1/x86_64/bdb00a07f2953a7285023a13b479e49ec6e919635a8f7f9e50ec31cfb492d4f2/x11-video-nvidiaG04-390.129-lp151.7.1.x86_64.rpm
    ./299/x11-video-nvidiaG04/390.129-lp150.6.1/x86_64/299c128d6e124b347c399ed2fd385c618740f8185263f62f9003dd7a0e3048e2/x11-video-nvidiaG04-390.129-lp150.6.1.x86_64.rpm
    Julio González Gil
    @juliogonzalez
    I was checking nvidia-glG04-390.129-lp151.7.1.x86_64.rpm :\
    megamaced
    @megamaced
    /var/spacewalk/packages/1/bdb/x11-video-nvidiaG04/390.129-lp151.7.1/x86_64/bdb00a07f2953a7285023a13b479e49ec6e919635a8f7f9e50ec31cfb492d4f2 # sha256sum x11-video-nvidiaG04-390.129-lp151.7.1.x86_64.rpm
    bdb00a07f2953a7285023a13b479e49ec6e919635a8f7f9e50ec31cfb492d4f2 x11-video-nvidiaG04-390.129-lp151.7.1.x86_64.rpm
    Also this returns nothing /var/spacewalk/packages/1 # find ./ -type d -name "49adadba5539df09ce6b2c38eec05fff19ecb84b587019ffb5457b8072843d2f"
    Julio González Gil
    @juliogonzalez
    interesting, can you download the package to the client, download only
    then run sha256sum there?
    megamaced
    @megamaced
    so I have no idea why zypper clients get 49adadba5539df09ce6b2c38eec05fff19ecb84b587019ffb5457b8072843d2f
    I downloaded from uyuni using web browser
    and ran sha256sum and it is correct
    Julio González Gil
    @juliogonzalez
    :-|
    megamaced
    @megamaced
    btw, it isn't just x11-video-nvidiaG04
    Julio González Gil
    @juliogonzalez
    try to download it with zypper in -d <package>
    then check the cache repo for zypper
    megamaced
    @megamaced
    nvidia-computeG04, nvidia-gfxG04-kmp-default, nvidia-glG04 and x11-video-nvidiaG04 all have wrong checksum through zypper
    Julio González Gil
    @juliogonzalez
    I'd also suggest -v
    s/cache repo/cache dir/
    it's at /var/cache/zypp/packages IIRC
    megamaced
    @megamaced
    i get the checksum error, then I can only choose discard
    /var/cache/zypp/packages is empty
    Julio González Gil
    @juliogonzalez
    [15:39] <megamaced> [edit] However if you made certain that the file with checksum '49ad..' is secure, correct
    [15:39] <megamaced> [edit] and should be used within this operation, enter the first 4 characters of the checksum
    [15:39] <megamaced> [edit] to unblock using this file on your own risk. Empty input will discard the file.`
    you should be able to force it with that
    -f will not help it seems doesn't work in this case, and neither --allow-unsigned-rpm
    I guess that message came from an interactive run and you could type 49ad and hit enter? :-?
    megamaced
    @megamaced
    yep, it will install fine if I force it etc
    but we have 30 users
    on opensuse leap 15.1 on uyuni
    the leap 15.0 users don't seem to be affected, at least no one mentioned anything :-D
    oh oh just had a thought, we are using Uyuni Proxy
    these clients are behind a uyuni proxy
    i bet that's where the problem is
    Julio González Gil
    @juliogonzalez
    no, not installing
    if you use -d it will only download the package, it will not install it
    megamaced
    @megamaced
    yes confirmed the issue was the Uyuni Proxy
    I did spacewalk-proxy stop, then rm -rf /var/cache/squid, then spacewalk-proxy start
    now clients can install nvidia drivers correctly
    Julio González Gil
    @juliogonzalez
    I wonder if the explanation is somehow related to what I commented above, about the packages being republished, and then the proxy not resyncing because version and release are the same
    mmmmmmm, but no, it's squid
    I don't think it trusts the filename only
    too late, but if it happens again, let us know if you see something at the squid logs
    maybe there's something that can be done to detect such situations and warn the administrator