Bug 674042 - Host don't poweroff when libvirt iSCSI pools are active
Summary: Host don't poweroff when libvirt iSCSI pools are active
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Martin Hoyer
URL:
Whiteboard:
Depends On:
Blocks: 846704 961026 1164899 1268411 1324930
TreeView+ depends on / blocked
 
Reported: 2011-01-31 12:46 UTC by Juan Quintela
Modified: 2017-06-07 16:38 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-26 21:22:11 UTC
Target Upstream Version:


Attachments (Terms of Use)
Oops during halt (4.38 KB, text/plain)
2011-02-01 12:41 UTC, Juan Quintela
no flags Details

Description Juan Quintela 2011-01-31 12:46:00 UTC
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.

Comment 2 Daniel Berrangé 2011-01-31 13:30:19 UTC
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 3 Juan Quintela 2011-02-01 12:41:57 UTC
Created attachment 476383 [details]
Oops during halt

Comment 4 Juan Quintela 2011-02-01 12:47:26 UTC
Retried, so far:
* RHEL5.6 works
* Fedora 14 work (at some point got fixed)
* RHEL6.0 and RHEL6.1 fails

Comment 5 Dave Wysochanski 2011-02-07 22:18:22 UTC
I'm not sure this is a libvirt issue - see https://bugzilla.redhat.com/show_bug.cgi?id=672530

Comment 6 RHEL 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.

Comment 7 Dave Allan 2011-06-08 21:08:24 UTC
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.

Comment 8 Mike Christie 2011-06-08 21:23:46 UTC
(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?

Comment 9 Suzanne Logcher 2011-10-06 18:53:47 UTC
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.

Comment 10 Vadym Chepkov 2012-06-28 19:19:22 UTC
I still use rm /etc/rc[06].d/*network as a workaround.
It's a problem in 6.3 as well

Comment 11 RHEL 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 12 RHEL 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.

Comment 16 Chris Leech 2015-11-03 05:56:08 UTC
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.

Comment 17 Martin Hoyer 2015-11-04 11:43:43 UTC
Hi Juan,
Is this still reproducible on Your side?

Comment 19 Tom Coughlan 2016-09-26 21:22:11 UTC
(In reply to Martin Hoyer from comment #17)
> Hi Juan,
> Is this still reproducible on Your side?

No reply since Nov.. Closing.


Note You need to log in before you can comment on or make changes to this bug.