preupgrade script reports "If it is a system partition then in-place upgrade is not possible."

Solution Unverified - Updated -

Issue

  • In the process of upgrading our systems to RHEL7, following the useful instructions from solution article number 637583.
    We use encrypted root partitions. The preupg too reports these as "If it is a system partition then in-place upgrade is not possible."

Running redhat-upgrade-tool --force then creates a new /boot/grub/grub.conf entry "System Upgrade." As kernel parameters it copies the previous ones, "rd_LUKS_UUID=luks-09040e1f...", which indeed don't work.

However, when changing the parameter name from "rd_LUKS_UUID" to "rd.luks.uuid", I can boot from the system upgrade kernel/ramdisk, and the upgrade scripts seem to run fine!

Therefore, it appears that it is actually easily possibly to do an in-place upgrade, contrary to what preupg is saying. Or, is this a bit good to be true? What other issues might appear when doing the upgrade with a LUKS-encrypted root volume?

Environment

  • Red Hat Enterprise Linux (RHEL) 7.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.