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.
Description of problem:
Poweroff (halt) hangs the host if an iscsi pool is used on libvirt.
Version-Release number of selected component (if applicable):
libvirt-0.8.7-3.el6.x86_64
kernel-2.6.32-94.el6.x86_64
It also happens with rhel6.0 & Fedora14 packages.
How reproducible:
Always.
Steps to Reproduce:
1. create a pool from iscsi
2. poweroff machine
3. Hangs with attached error (a timeout)
Actual results:
Machine don't end poweroff, stays hanged on halt printing the attached bug once each 120 seconds
Expected results:
Machine powersoff correctly.
Additional info:
Why do I think the problem is with libvirt? because if I do:
virsh pool-destroy <iscsi pools>
And now I poweroff, it poweroff correctly.
You've not actually attached the details of the bug you mentioned you would...
How are you triggering the shutdown ? Are you doing a controlled shutdown using 'shutdown -h' ? Can you confirm whether the iscsi initscripts are running during shutdown ?
This is unlikely to be a libvirt bug. It simply calls out to the iscsiadm toolset.
Comment 6RHEL Program Management
2011-04-04 02:04:46 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
I'm pretty sure this is not a libvirt problem. I'm reassigning to iscsi for further investigation. It smells a lot like BZ 566772 to me, but I don't have any real evidence to believe that's the case.
(In reply to comment #2)
> 'shutdown -h' ? Can you confirm whether the iscsi initscripts are running
> during shutdown ?
Screen shot in comment #3 shows iscsi sessions still running when the network has been shutdown. We have got to the final part of the shutdown, kernel shutdown. iscsi really wants to send the sync cache command to make sure data is synced up and we are hung there.
Normally iscsi init scripts run before the kernel and network is shutdown. Those init scripts stop the sessions and send the sync cache command.
In 6.0 there were some shutdown bugs where if service iscsi start had not started the session then they would not get shutdown cleanly like in this bz. So, if you just used iscsiadm to libiscsi to create the session then they might not get shutdown cleanly. In 6.1 these should be fixed.
What is the iscsi initiator-utils tools version? Is it iscsi-initiator-utils-6.2.0.872-21.el6?
Are you doing iscsi root/boot?
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
I still use rm /etc/rc[06].d/*network as a workaround.
It's a problem in 6.3 as well
Comment 11RHEL Program Management
2012-12-14 07:57:55 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 12RHEL Program Management
2013-10-14 05:21:02 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I've played around a bit with a few different 6.x installs, and can't reproduce this just by having a libvirt iscsi pool active. I'm not sure it's still an issue or not.