[Bug 1014470] New: Yast2 Wrong Digest for packages.gz using default repo in openQA
http://bugzilla.suse.com/show_bug.cgi?id=1014470 Bug ID: 1014470 Summary: Yast2 Wrong Digest for packages.gz using default repo in openQA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: normand@linux.vnet.ibm.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Yast2 Wrong Digest for packages.gz using default repo in openQA as reported by attached yast2_wrong_digest.png I regularly have such problem while testing in my openQA local instance using default Tumbleweed repository address. looking at y2log, the failure is reported after the third download === $grep packages.gz YaST2/y2log |grep -E 'Downloader|Checking|FileChecker' 2016-12-08 02:10:42 <1> install(3308) [zypp] Downloader.cc(download):159 adding job packages.gz 2016-12-08 02:10:42 <1> install(3308) [zypp:fetcher] Fetcher.cc(validate):392 Checking job [/var/cache/zypp/raw/openSUSE-20161208-0JtHXIm/suse/setup/descr/packages.gz] (1 checkers ) 2016-12-08 02:11:04 <1> install(3308) [zypp] Downloader.cc(download):159 adding job packages.gz 2016-12-08 02:11:05 <1> install(3308) [zypp:fetcher] Fetcher.cc(validate):392 Checking job [/var/cache/zypp/raw/openSUSE-20161208-0cDLjJW/suse/setup/descr/packages.gz] (1 checkers ) 2016-12-08 02:28:44 <1> install(3308) [zypp] Downloader.cc(download):159 adding job packages.gz 2016-12-08 02:28:53 <1> install(3308) [zypp:fetcher] Fetcher.cc(validate):392 Checking job [/mnt/var/cache/zypp/raw/repo-ossrM4uda/suse/setup/descr/packages.gz] (1 checkers ) 2016-12-08 02:28:53 <2> install(3308) [FileChecker] FileChecker.cc(operator()):55 File /mnt/var/cache/zypp/raw/repo-ossrM4uda/suse/setup/descr/packages.gz has wrong checksum sha256-0b0c779ffcc12e146b2de2c9c4bb19ac28d9dd1992556f1e1ea1a29086e5fee6 (expected sha256-c0034264db43bc1238dd0bc3e9230a3650d5aafa497ee47f502afaa986e0fd2c) === -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c1
--- Comment #1 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c2
--- Comment #2 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c3
--- Comment #3 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c4
--- Comment #4 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c5
Oliver Kurz
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c6
--- Comment #6 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c7
--- Comment #7 from Oliver Kurz
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c8
--- Comment #8 from Michel Normand
Right. Is it reproducible on the same package? On each installation? Anyway, you could also apply a workaround using openQA, of course.
It is not same package on each trials. I am not able to access openQA.o.o instance to manually issue a command without SUSEMIRROR like the following. Could you do that for me ? I am only allowed to restart/start tests via the WebUI === /var/lib/openqa/script/client isos post ISO=openSUSE-Tumbleweed-DVD-ppc64le-Snapshot20161212-Media.iso DISTRI=opensuse VERSION=Tumbleweed FLAVOR=DVD ARCH=ppc64le BUILD=20161212 TEST=boot_to_snapshot === . -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1014470
Imobach Gonzalez Sosa
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c9
Oliver Kurz
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c10
Michel Normand
I did, see https://openqa.opensuse.org/tests/321084 based on current Tumbleweed snapshot from today.
Thanks Oliver, this good result in openQA.o.o instance (using now the default repo), let me guess the problem is really between Yast/libzypp and the MirrorBrain on this repo (http://download.opensuse.org/...) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c11
--- Comment #11 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c12
Imobach Gonzalez Sosa
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c13
Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c14
--- Comment #14 from Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c15
Michel Normand
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c16
--- Comment #16 from Michel Normand
Somehow this issue got stuck.
Does this still happen?
Yes it is, with Snapshot 20170411, with data reported in comment #15
Can you eliminate the possibility that this is a server-side problem, or a problem of a possible proxy configuration or load balancer?
The problem do not appear with same snapshot in openQA.o.o https://openqa.opensuse.org/tests/385525#step/start_install/7 But is systematic now with my own instance of openQA that is outside Suse network.
Did this happen only once, or does it happen on a regular basis?
I am not 100% sure how atomic Tumbleweed updates are; I would assume that all the files (including the digests / md5sums / sha256sums etc.) are generated into a new directory, and then that new directory is renamed, so all changes are visible at the same time. I am pretty sure that this is how it is done for our SUSE servers. Did you use one of them, or did you use your own mirror? If yes, is it possible that you just caught the period where that server was updated (with rsync or whatever) so there was a short time when the server's content was inconsistent? (Newer files but still old digests or the other way round).
I do not specify any specific repository and only using default setup for install. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1014470
http://bugzilla.suse.com/show_bug.cgi?id=1014470#c17
Michel Normand
participants (1)
-
bugzilla_noreply@novell.com