Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1749100[details]
screenshot during hang
Description of problem: post-kickstart hangs shutting down: "failed deactivating swap"
Version-Release number of selected component (if applicable):
How reproducible: every time
Steps to Reproduce:
1.Install RHEL8 via kickstart
2.Wait...
3.
Actual results: After kickstart has installed in the OS, it correctly tries to shut down and reboot. But the shutdown process hangs with a set of six cycling messages, which include "failed deactivating swap /dev/dm-6" and similar. The hang lasts for many tens of minutes. (A colleague who was patient enough to wait reports at least two and a half hours.) We have to force a power cycle of the VM to continue.
Expected results: Shutdown with kickstart should succeed in decent time, not several hours.
Additional info: It looks like a bugzilla that was reported on Fedora but which had been closed because that version of Fedora was EOL. https://bugzilla.redhat.com/show_bug.cgi?id=1680460
Yes, reproducible.
Example. Need a kickstart client machine or VM with small memory (the idea being to ensure that something goes into swap) and any reasonable size kickstart file (typical server or typical workstation).
Have some sort of "%post" that will take an elapsed time for allowing monitoring. Something as simple as "sleep 900" (15 minutes) is probably sufficient.
Begin to kickstart that client.
Once that kickstart is going, e.g. started to install packages, switch to an alternate screen (that offers a linux prompt).
(Be comfortable with flipping back and forth between those two screens.)
From that alternate screen, monitor swap usage, e.g. "swapon --summary" or similar.
Hopefully you will see it occupy some real swap space.
When kickstart enters "%post" (e.g. after seeing on the main screen that it has finished its packages), verify swap is occupying real swap space.
Then at the alternate console do "swapoff -a" (which triggers asynchronous removal of swap space)...
... and see how SLOWLY that swap use reduces (monitoring with that "swapon --summary" or similar).
It is that slowness which is the issue.
I hope that helps.
(In reply to David Lee from comment #0)
> But the shutdown process hangs with a set of six
> cycling messages, which include "failed deactivating swap /dev/dm-6" and
> similar.
What are the other messages? This comes from systemd-shutdown, but it definitely shouldn't cycle infinitely. The unmounting loop should be terminated if nothing has been unmounted/deactivated in the current run. And I see no obvious problems with the code.
> Example. Need a kickstart client machine or VM with small memory
How small is "small"? Can't you just show your configuration to save us time?
Comment 5RHEL Program Management
2022-07-20 07:27:56 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.