Description

The in-place upgrade process needs to be non-interactive and must not require user presence at the system. In general with LUKS encrypted devices the non-interactivity prerequisite can not be satisfied (there are special cases with extensions built on top of libcryptsetup that may already work). Use this epic to track steps necessary to enable in-place upgrade of RHEL using encrypted storage.

There are exceptions and for example LUKS encrypted storage for ceph fs can be upgraded. But this is due to fact that ceph manages own 'keyfiles' and therefore does not rely on interactive passphrase prompts.

Acceptance Criteria

A list of specific needs or objectives must be delivered to satisfy the epic.

• Investigate impact on customers due to current state. How big of an issue it is that we can not use in-place upgrades with LUKS encrypted storage in general.
• Identify missing functions and/or areas that remedy for this issue would impact
• Estimate time needed to complete the epic (may involve multiple components)

What SSTs and Layered Product teams should review this?