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.
Bug 842750 - [RHEV] Sanlock daemon can not be stopped running service sanlock stop because lockspaces still exist.
Summary: [RHEV] Sanlock daemon can not be stopped running service sanlock stop because...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks: 800588
TreeView+ depends on / blocked
 
Reported: 2012-07-24 14:11 UTC by Leonid Natapov
Modified: 2012-09-23 15:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-23 15:05:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (1.08 MB, application/octet-stream)
2012-07-24 14:11 UTC, Leonid Natapov
no flags Details

Description Leonid Natapov 2012-07-24 14:11:25 UTC
Created attachment 600036 [details]
logs

Sanlock daemon can not be stopped running 'service sanlock stop' because lockspaces still exist. We need to take care of the lockspaces and remove them  upon stopping sanlock daemon or forcibly shut down the sanlock daemon which will automatically remove any remaining lockspaces.


logs attached

Comment 2 David Teigland 2012-09-20 21:17:29 UTC
Can we close this bz?  I don't think this is a bug.

Comment 3 Leonid Natapov 2012-09-23 15:05:09 UTC
when there are no leases sanlock service can be successfully stopped running service sanlock stop.

when there are active leases service can not be stopped which is seems to be correct behavior.
closing this bz as not a bug.


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