[Bug 1178233] New: zypper up does not report any updates in WSL after longer pause
https://bugzilla.suse.com/show_bug.cgi?id=1178233 Bug ID: 1178233 Summary: zypper up does not report any updates in WSL after longer pause Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: WSL Assignee: sle-ms@suse.de Reporter: lubos.kocman@suse.com QA Contact: qa-c@suse.de Found By: --- Blocker: --- I do have WSL images with Leap 15.2 and it seems that zypper doesn't register outdated repodata cache. Let's say that I'd start WSL image (bash session) once per two weeks, and if I simply run "zypper up" after these two weeks zypper reports no update, until I clean repodata I didn't call refresh simply up && clean --all && up and that worked fine. However I'd like to avoid situation when zypper simply reports no update with sporadically WSL use and user gets to believe it. My initial thought it's that this is caused by not having any services running inside the "container", however Ludwig things something might be wrong with the date/time inside the image. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178233
Lubos Kocman
https://bugzilla.suse.com/show_bug.cgi?id=1178233
https://bugzilla.suse.com/show_bug.cgi?id=1178233#c26
--- Comment #26 from Maintenance Automation
https://bugzilla.suse.com/show_bug.cgi?id=1178233
https://bugzilla.suse.com/show_bug.cgi?id=1178233#c27
--- Comment #27 from Maintenance Automation
https://bugzilla.suse.com/show_bug.cgi?id=1178233
https://bugzilla.suse.com/show_bug.cgi?id=1178233#c28
--- Comment #28 from Maintenance Automation
https://bugzilla.suse.com/show_bug.cgi?id=1178233
https://bugzilla.suse.com/show_bug.cgi?id=1178233#c29
Michael Andres
Just reporting that this is no longer reproducible with these versions (and obviously all other updates to the underlying WSL...)
libzypp-17.31.8-1.1.x86_64 zypper-1.14.59-1.3.x86_64
Want to keep it open for further investigation or call it done?
Closing it. Please reopen if it happens again. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com