[Bug 1198978] New: Upgrade Leap 15.2->15.3 apparently incomplete
https://bugzilla.suse.com/show_bug.cgi?id=1198978 Bug ID: 1198978 Summary: Upgrade Leap 15.2->15.3 apparently incomplete Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs@suse.de Reporter: bryan.gartner@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- For an existing instance of Leap 15.2, trying to migrate/upgrade to 15.3, following steps documented in https://en.opensuse.org/SDB:System_upgrade, e.g. zypper --releasever=15.3 dup --download-in-advance Once that completes and system is rebooted, this is still the case node:~> more /etc/os-release NAME="openSUSE Leap" VERSION="15.2" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.2" PRETTY_NAME="openSUSE Leap 15.2" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.2" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" And this remains the same even after a follow-on of zypper ref; zypper patch ; reboot as well. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c1 Lubos Kocman <lubos.kocman@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lubos.kocman@suse.com --- Comment #1 from Lubos Kocman <lubos.kocman@suse.com> --- Hello my first thought is to follow this https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.3/#sec.upgrad... The 15.2 system needs to have latest zypper which fetches gpgkeys from repodata. Otherwise user has to specify --alow-vendor change to allow exchange of openSUSE signed rpms to SUSE signed and vice versa. I would also recommend to provide zypper logs and output from the dup without that we are only guessing. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c2 --- Comment #2 from Lubos Kocman <lubos.kocman@suse.com> --- If the system was not upgraded then followup commands will still reference the 15.2 repos. Another request from my side would be to show urls of repos that system is using. In case that repo files use hardcoded version (e.g. custom mirror entries) the --releasever has nothing to substitute and will still reference 15.3. Following is the example of correctly defined url (uses $releasever instead of 15.3). from $ grep baseurl * /etc/zypp/repos.d/*.repo ... /etc/zypp/repos.d/repo-oss.repo:baseurl=http://download.opensuse.org/distribution/leap/$releasever/repo/oss/ ... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c3 --- Comment #3 from Bryan Gartner <bryan.gartner@suse.com> --- Already sent these steps to partner as well - please check all of the repo files in /etc/zypp/repos.d/* and ensure that there is not a text element of 15.2 in the URLs. If there is, please do the Step 5 from the document (sed) to replace those and retry the dup - also try a modified dup command to see if this addresses the issue zypper dup --releasever 15.3 --allow-vendor-change --dlownload-in-advance And after they try/reply, will follow-up to get more details/logs if needed -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c4 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bryan.gartner@suse.com, | |chcao@suse.com Flags| |needinfo?(bryan.gartner@sus | |e.com) --- Comment #4 from Chenzi Cao <chcao@suse.com> --- Hi Bryan, is the upgrading issue resolved or not please? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c5 --- Comment #5 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858908 --> https://bugzilla.suse.com/attachment.cgi?id=858908&action=edit pre-dup supportconfig -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c6 --- Comment #6 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858909 --> https://bugzilla.suse.com/attachment.cgi?id=858909&action=edit post-dup supportconfig -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c7 --- Comment #7 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858910 --> https://bugzilla.suse.com/attachment.cgi?id=858910&action=edit post-dup.rpm -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c8 --- Comment #8 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858911 --> https://bugzilla.suse.com/attachment.cgi?id=858911&action=edit pos-dup.os-release -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c9 --- Comment #9 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858912 --> https://bugzilla.suse.com/attachment.cgi?id=858912&action=edit post-dup-patch supportconfig -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c10 --- Comment #10 from Bryan Gartner <bryan.gartner@suse.com> --- Created attachment 858913 --> https://bugzilla.suse.com/attachment.cgi?id=858913&action=edit post-patch.up -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c11 --- Comment #11 from Bryan Gartner <bryan.gartner@suse.com> --- (In reply to Chenzi Cao from comment #4)
Hi Bryan, is the upgrading issue resolved or not please?
FWIW, the initial issue encountered by this partner was they were using local mirrors of our repos and these were incomplete). With that said, I just did a re-try of doing an upgrade of - Leap 15.2, doing a very basic VM install (Server pattern) - (see pre-dup supportconfig) - used doc steps - zypper --releasever=15.3 refresh - zypper --releasever=15.3 dup --download-in-advance - reboot - still cited as 15.2 (see post-dup.os-release) - 30 pkgs still show lp152 (see post-dup.rpm) - (see post-dup supportconfig) - tried - zypper ref ; zypper patch - only one pkg patched (and still shows 15.2) - (see post-dup-patch supportconfig) - zypper ref ; zypper up - no changes, 35 not installed - 2 repos listed as outdated - (see post-patch.up) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 Bryan Gartner <bryan.gartner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bryan.gartner@sus | |e.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c12 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |lubos.kocman@suse.com Flags| |needinfo?(bryan.gartner@sus | |e.com) --- Comment #12 from Chenzi Cao <chcao@suse.com> --- @Bryan, I found a upgrade doc about How to upgrade from openSUSE Leap 15.0 to 15.1, I used the same steps to upgrade my laptop from Leap15.2 to Leap15.3, it worked well, would you like to have a try? https://linuxkamarada.com/en/2019/05/27/how-to-upgrade-from-opensuse-leap-15... @Lubos, would anyone provide a Leap upgrade guide please? Or shall I assign the bug report to documentation team to write an official upgrade guide? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198978 https://bugzilla.suse.com/show_bug.cgi?id=1198978#c13 --- Comment #13 from Bryan Gartner <bryan.gartner@suse.com> --- @Chenzi ... a few more observations - for some reason, when freshly deploying a VM (with Leap 15.2 NET ISO) on a KVM host, after the install completed, the ISO remained an enabled repo and mountable, plus I didn't do the sed to modify that repo (since all the other repos had the the $releasever entry in the baseurls) - given that glitch, the upgrade to 15.3 (following in initial doc link) still ended up with /etc/os-release citing 15.2 - disabling that repo and retrying the migration did kind of work, however one still needs to do a follow-up zypper ref ; zypper patch after the reboot to get the vast number of SLE-provided basic packages upgraded as well to complete finish the dup/migration - doing another fresh 15.2 install, and then disabling/removing that repo/media from the VM before attempting the upgrade process then works fine ... albeit still makes sense to do the zypper ref; zypper patch to finish the all packages aspect ( 424 packages to upgrade, 11 new, 19 to remove ) - and FWIW, I have not had this main issue when doing multiple 15.3 -> 15.4 migration/upgrades So will leave it up to you to validate/disect - the 15.2 VM retained post-install ISO/repo issue - and/or just close this BZ -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com