** Description changed: [Impact] * Using the device name on the kernel cmdline in the resume= option leads to failure to resume from hibernation when the device name is not stable, which can be the case for nvme drives. [Test Case] * Set up an EC2 instance to allow hibernation * Wait for hibinit-agent.service fully started * /etc/default/grub.d/99-set-swap.cfg should refer to the resume= partition by PARTUUID [Regression Potential] * Failure to discover PARTUUID makes the system unable to resume. A potential crash would cause the system unable to set up hibernation or - unable to resume. + unable to resume. (On Focal PARTUUID is already in use, even without + this fix.) [Original Bug Text] When the agent inserts the resume device path and offset into the kernel cmdline, it uses device names such as the following: `resume_offset=223232 resume=/dev/nvme1n1p1` The issue is that `/dev/nvme1n1p1` is not static. On the reboot, the block device may appear at `/dev/nvme0n1p1` resulting in failure to find the swapfile used to suspend. The solution should be to use a persistent block device naming scheme.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896638 Title: Path to swapfile doesn't use a static device path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
