Comment # 8 on bug 1115188 from Martin Vidner

Thanks, the logs do record the error (y2log-1.gz)

I can see that the network provides the problematic file:
2018-11-02 15:23:10 <1> install(2665) [zypp++]
MediaCurl.cc(doGetFileCopyFile):1511 URL:
http://download.opensuse.org/ports/ppc/update/tumbleweed/repodata/d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3-primary.xml.gz
2018-11-02 15:23:10 <1> install(2665) [zypp++]
MediaMultiCurl.cc(doGetFileCopy):1373 HTTP response: 200

And then we see that YaST detects a problem with a signed file:
2018-11-02 15:23:12 <2> install(2665) [FileChecker]
FileChecker.cc(operator()):64 File
/mnt/var/tmp/AP_0xoR0n8U/repodata/d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3-primary.xml.gz
has wrong checksum
sha256-efc4a80695dc0f8fdfe44f76872170e897355aa0fcdf9b760587b75bf6ae7fc3
(expected
sha256-d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3)

Then I see that we've shown you a notice that the checksum is wrong, and you
choose to proceed anyway:
https://github.com/yast/yast-yast2/blob/dc62fa4903fdccdde15f5dacc8456f06a2c55e5a/library/packages/src/modules/SignatureCheckDialogs.rb#L762
2018-11-02 15:23:12 <1> install(2665) [Ruby]
modules/SignatureCheckDialogs.rb:237 CHECK_SIGNATURES: yes
2018-11-02 15:23:31 <1> install(2665) [Ruby]
modules/SignatureCheckDialogs.rb:94 User decision to show dialog
'-AcceptWrongDigest-' for
'/mnt/var/tmp/AP_0xoR0n8U/repodata/d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3-primary.xml.gz'
again is 'false'
2018-11-02 15:23:31 <1> install(2665) [Ruby]
modules/SignatureCheckDialogs.rb:153 User decision in default return for
'-AcceptWrongDigest-' for
'/mnt/var/tmp/AP_0xoR0n8U/repodata/d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3-primary.xml.gz'
is 'true'
2018-11-02 15:23:32 <2> install(2665) [FileChecker]
FileChecker.cc(operator()):72 User accepted
/mnt/var/tmp/AP_0xoR0n8U/repodata/d95cab3de048d47ff0fd44c8f28f2182f1fbf2f6361dba6f930d7cc9ab2537d3-primary.xml.gz
with WRONG CHECKSUM.


So, your network filter replaced a legitimate file with an error notice while
returning a 200 OK status code. YaST has told you that it got wrong input as
soon as it saw it, and you proceeded anyway, then it reported another error,
quite a readable one IMHO.

I believe that YaST is behaving fine here.