Asking for review of a check off list for upgrade to Leap 16.0

After two failed Leap 16.0 upgrades, I used Gemini AI to help me draft a check-off list to successfully make this upgrade. I first of all have to replace my Nvidia GeForce GT710 video card, I have a Radeon RX-550 card ordered and I will make sure that this is running okay in Leap 15.6 and delete the Nivida repository.

After that, here is the check list:

=== LEAP 15.6 TO 16.0 MIGRATION PROTOCOL ===
File Reference: update-leap.txt

PHASE 1: PREPARATION (Inside the Graphical Desktop)
--------------------------------------------------------------------------------
1. Take a snapshot of all currently installed package versions:
   sudo rpm -qa --qf "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" | sort > /root/packages_before_upgrade.txt

2. Freeze and backup your current Leap 15.6 repository configurations:
   sudo /root/repo-manager.sh backup

3. Manually disable all third-party repositories to prevent dependency locks:
   sudo zypper mr -d packman brave_browser code google-chrome opera NVIDIA:repo-non-free.repo_1 lynis home_maxiotis

4. Take your pristine Snapper baseline snapshot (Note the ID number it prints!):
   sudo snapper create --type pre --print-number --description "Latest Leap 15.6" --cleanup-algorithm number

PHASE 2: TRANSITION TO THE CLI (Virtual Consoles)
--------------------------------------------------------------------------------
5. Drop to a raw text terminal by pressing: Ctrl + Alt + F2
   Log in directly as the 'root' user.

6. Cleanly isolate the system and kill the graphical desktop session completely:
   systemctl isolate multi-user.target


PHASE 3: THE UPGRADE EXECUTION
--------------------------------------------------------------------------------
7. Set up the live background error tracking:
   - Press Ctrl + Alt + F3 to open a second terminal.
   - Log in as 'root'.
   - Run the following command to track systemd journal errors in real-time:
     journalctl -f -p 3 -o short-precise > /root/migration_journal.log

8. Launch the migration tool with persistent session logging:
   - Press Ctrl + Alt + F2 to switch back to your first terminal window.
   - Execute the migration utility:
     opensuse-migration-tool 2>&1 | tee /root/migration_attempt.log


PHASE 4: POST-MIGRATION / CONTINGENCY RECOVERY
--------------------------------------------------------------------------------
9. If the migration tool finishes cleanly with no errors:
   reboot

10. If the machine fails to boot or crashes during the subsequent reboot:
    - Boot using a recovery USB or select a read-only snapshot from the GRUB menu.
    - Drop to a command line and pull the crash log from the failed boot attempt immediately:
      sudo journalctl -b -1 > /root/previous_boot.log

11. If you need to roll back and restore your 15.6 repositories after a filesystem revert:
    sudo /root/repo-manager.sh restore

================================================================================

Is there anything I am missing or overlooking? I do want solid logs in case this upgrade fails.

I appreciate comments by the openSuse Linux gurus.

Randall

Instead of letting others do the reading of this long AI generated text, would it not have been better that you detected the differences between it and https://en.opensuse.org/SDB:System_upgrade , and then maybe ask here if those differences are a real improvement?

3 Likes

I’m curious as to what the contents of /root/repo-manager.sh would be?

Are you a bit sarcastic? :rofl:

BTW, in my opinion this should be in Open Chat.

To @American_Citizen …

So, you’re replacing the NVIDIA card (don’t blame you) and you will delete the NVIDIA repo (paragraph one).
However, in Phase I, Step 3, you’re gonna disable Packman and an NVIDIA repo.
I would think, based on paragraph one, those repos would already have been removed (?)

What will “packages_before_upgrade.txt” (Phase I Step 1) be used for (not obvious, unless I missed it)?

In reference to Phase I, Step 4, what will it be used for in the potential future (again, unless I missed its potential use)?

brave_browser.repo                openSUSE:repo-openh264.repo           openSUSE:update-non-oss.repo
code.repo                         openSUSE:repo-oss-debug.repo          openSUSE:update-oss-debug.repo
google-chrome.repo                openSUSE:repo-oss-source.repo         openSUSE:update-oss.repo
home_maxiotis.repo                openSUSE:repo-oss.repo                openSUSE:update-sle-debug.repo
lynis.repo                        openSUSE:update-backports-debug.repo  openSUSE:update-sle.repo
openSUSE:repo-non-oss-debug.repo  openSUSE:update-backports.repo        opera.repo
openSUSE:repo-non-oss.repo        openSUSE:update-non-oss-debug.repo    packman.repo

is what this folder current contains (plus a few more rpmsave files)

If you look at the repo folder, I have other software repos besides opensuse

That’s likely to produce no response. IME, that’s where SDDM and GDM run. F3-up should work though, barring something interfering with Ctrl-Alt-*.

Yep, but as I referenced , the list is redundant per paragraph one - should already have been deleted.

sudo zypper mr -d
… “packman” (<== or maybe not used for NVIDIA?)
… “NVIDIA:repo-non-free.repo_1”

Was this directed at me? I was being serious.

Sorry, then I misinterpreted.